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 ]
Jan Zorz @ go6.si
jan at go6.si
Sun Jan 9 23:10:25 CET 2011
On 9.1.2011 22:32, kzorba at otenet.gr wrote: >> If you did some stuff in that direction, can you send what you extracted from >> other sections and in your opinion fits the CPE requirements. >> > > Since I am out of the office these days, I will get back to you with this in the > following days. > Another colleague gathered the requirements and we also consulted IETF documents > from what I know. Kostas, hi. Thnx, appreciated. > >> All ideas and preliminary draft texts helps to go forward with the 501 doc. >> > > From what I understood in the discussions of the thread, the idea will be to > provide pointers in the 501 doc to IETF documents, right? Some people expressed > concerns that the RIPE document should not duplicate IETF work or come up with > any sort of differences. > Of course the 501 doc is not any form of standard, just some work that will help > in moving IPv6 deployment a bit closer... 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 ]