fundamental brokenness of iasa2 updates (was Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



this is a separate issue about the iasa2 proposed updates

come on - you update an RFC without including a section that says what changes you are making???

are you purposely trying to make it harder for IETF participants to understand what’s going on?

every RFC that updates another RFC needs (MUST?) have a section that tells the reader what has
changed - this is vital for any technical speck so the implementor knows what they have to change in
their implementation but its also very important in process documents so participants can understand 
if they need to change how they do things

so, be nice to the participants and admit (in writing) what changes you are proposing

Scott






[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux