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 21:56:19 CET 2011
On 8.1.2011 12:11, kzorba at otenet.gr wrote: > Greetings to all and happy new year. > > We also used this document to extract basic features (in our environment) > for customer CPEs. > In my opinion, the "document" format must be preserved as a single place to > contain the entire information. I guess 'if' statements like Jan mentions is > one way to achieve the desired outcome. Kostas, hi. 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. All ideas and preliminary draft texts helps to go forward with the 501 doc. Regards, Jan P.S: Did we met in Athens at v6 TF meeting last summer?
- 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 ]