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 ]
Anfinsen, Ragnar
Ragnar.Anfinsen at altibox.no
Mon Jan 10 09:35:14 CET 2011
Hi Jan, > 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? I think the best way is to point to the IETF document. There are no reason to duplicate the work, especially while it is in draft. I suggest that we work with the second update of the RIPE-501 document with the "Basic Requirements for IPv6 Customer Edge Routers" draft ans mandatory, and keep the updated RIPE document in draft until the IETF document gets a RFC number. When this is done there are no need to do any changes to the RIPE document if the IETF document changes. So my suggestion is to only refer to the IETF document, not to duplicate it. Best Regards Ragnar Anfinsen Network Engineer Altibox AS
- 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 ]