Re: PaceJoinSectionSixAndTen
-1. IETF documents have to have a Security Considerations section that describes general security issues. In no cases that I know of do they contain protocol specification. See RFC 3552 for more info. --Paul Hoffman, Director --Internet Mail Consortium
Re: PaceJoinSectionSixAndTen
Paul Hoffman wrote: -1. IETF documents have to have a Security Considerations section that describes general security issues. In no cases that I know of do they contain protocol specification. See RFC 3552 for more info. Is that -1 to the proposed title or -1 to having one section? cheers Bill
Re: PaceJoinSectionSixAndTen
At 5:09 PM + 2/7/05, Bill de hÓra wrote: Paul Hoffman wrote: -1. IETF documents have to have a Security Considerations section that describes general security issues. In no cases that I know of do they contain protocol specification. See RFC 3552 for more info. Is that -1 to the proposed title or -1 to having one section? The latter. In IETF documents, there should be a section that tells you how to do security, and another section that shows the bigger picture about security (such as known threats, other interesting security work, and so on). --Paul Hoffman, Director --Internet Mail Consortium
Re: PaceJoinSectionSixAndTen
Paul Hoffman wrote: The latter. In IETF documents, there should be a section that tells you how to do security, and another section that shows the bigger picture about security (such as known threats, other interesting security work, and so on). I can tell this isn't worth arguing about :) I've withdrawn the pace and notified Sam. cheers Bill
Re: PaceJoinSectionSixAndTen
PaceJoinSectionSixAndTen -1