This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] "Requirements For IPv6 in ICT Equipment" comment
- Previous message (by thread): [ipv6-wg] "Requirements For IPv6 in ICT Equipment" comment
- Next message (by thread): [ipv6-wg] "Requirements For IPv6 in ICT Equipment" comment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ivan Pepelnjak
ip at ioshints.info
Mon Jan 10 08:46:47 CET 2011
Wouldn't it be easier to ask Ole to provide a list of mandatory and optional RFCs in his document than to extract them into another document (with all the resulting synchronization challenges)? > I'm still thinking and need a discussion first with authors and see what > community thinks - but pointing to RFC or draft is ok for us, we know how > to > read RFC and so on - problem is when somebody writes a tender for buying > ICT > equipment - in this case going to read RFC or draft or something might be > quite > complicated for some people. > > Not sure yet, do we just point to Ole's draft (that is excellent imho) or > do we > write a list of mandatory RFCs that are 1:1 in sync with the draft and BBF > paper > (Ole is also editing that) and keep the list in sync if draft/RFC changes. > This > way tender initiator can just copy/paste RFCs and this way the job is > easy. > > Any thoughts? > > Cheers, Jan
- Previous message (by thread): [ipv6-wg] "Requirements For IPv6 in ICT Equipment" comment
- Next message (by thread): [ipv6-wg] "Requirements For IPv6 in ICT Equipment" comment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]