Re: 1154bis quick analysis

We want to be sure to pick an algorithm that is
legally unencumbered in BOTH directions.  -- NB


Is there something available to further explain this statement?  It
is apparently a limitation put on by IETF.  It seems to be getting
in the way of specifying the system.  Has FSF-itis invaded the IETF?

For the purpose of building products it seems that whether something
is `legally encumbered' is not an issue, the licensing terms are 
the issue.

        David

<Prev in Thread]	Current Thread	[Next in Thread>
1154bis quick analysis, David Herron Re: 1154bis quick analysis, Nathaniel Borenstein Re: 1154bis quick analysis, t.l.hansen Re: 1154bis quick analysis, Keith Moore RE: 1154bis quick analysis, Ned Freed Re: 1154bis quick analysis, Beast (Donald E. Eastlake, 3rd) Re: 1154bis quick analysis, Keith Moore Re: 1154bis quick analysis, Nathaniel Borenstein Re: 1154bis quick analysis, David Herron <= Re: 1154bis quick analysis, Keith Moore Re: 1154bis quick analysis, John C Klensin Re: 1154bis quick analysis, Beast (Donald E. Eastlake, 3rd) Re: 1154bis quick analysis, Keith Moore Re: 1154bis quick analysis, John C Klensin Re: 1154bis quick analysis, David Herron Re: 1154bis quick analysis, David Herron Re: 1154bis quick analysis, henry Re: 1154bis quick analysis, Beast (Donald E. Eastlake, 3rd)

Previous by Date:	Re: Multipart/Mixed and Compound Documents, Bill Janssen
Next by Date:	Re: 1154bis quick analysis, David Herron
Previous by Thread:	Re: 1154bis quick analysis, Nathaniel Borenstein
Next by Thread:	Re: 1154bis quick analysis, Keith Moore
Indexes:	[Date] [Thread] [Top] [All Lists]