Fw: (IPng 7092) Current Agenda for First Day of IPng Interim Meeting
- Date: Wed, 27 Jan 1999 07:13:13 +0100
FYI.
Regards,
Thomas Trede
-----Urspr|ngliche Nachricht-----
Von: Bob Hinden hinden@localhost
An: ipng@localhost ipng@localhost;
ngtrans@localhost ngtrans@localhost
Cc: hinden@localhost hinden@localhost; deering@localhost
deering@localhost
Datum: Dienstag, 26. Januar 1999 22:58
Betreff: (IPng 7092) Current Agenda for First Day of IPng Interim Meeting
>Folks,
>
>Attached is the current agenda for the first day of the interim IPng and
>NGTRANS working group meetings, February 2-4, in Grenoble, France. Please
>send requests for changes to hinden@localhost and deering@localhost.
>
>*** Note 1 *** Several folks sent suggested agenda additions already, but
>in some cases, it was not clear which of the three days those topics best
>belonged to. If you sent a suggestion, and it has not appeared on any
>of the three agendas, please resend to the appropriate chair(s):
>
> Day 1: IPng working group (Deering & Hinden)
> Day 2: NGtrans working group (Fink & Hain)
> Day 3: Deployment & promotion (Bound)
>
>Also, there will be a chance to adjust the agendas further on the meeting
>days themselves, of course.
>
>*** Note 2 *** For the first day, we have written down some names of folks
>to lead discussions on particular topics. If one of those names is yours,
>and you don't want to lead those discussions, please let us know.
>
>Thanks,
>
>Bob Hinden
>Steve Deering
>
>
>Tuesday, February 2 -- IPng w.g. meeting
>----------------------------------------
>
> Purpose:
>
> The IPng w.g. has mostly completed its original charter, except for
> shepherding the many w.g. specs through the final stages of Internet
> Standardization. The purposes of this meeting are: (a) to review the
> state of our many documents to identify any holes or loose ends that
> must be finished up to complete our charter, and (b) to identify and
> discuss new IPv6-related topics that the attendees think should be
> taken on by the IETF or the IRTF (Internet Research Task Force),
> either in the current working group or in other working groups /
> research groups.
>
> Requirements for Attendees:
>
> **NOTE** All attendees are required to bring a short list (one to five
> items, on a single sheet of paper) of topics that they consider the
> most important IPv6-related topics for the IETF or IRTF to work on.
>
> Agenda:
>
> o Introduction (S. Deering)
>
> o Local arrangements (A. Durand)
>
> o Collect attendee required issue lists (S. Deering)
>
> o Review and update agenda (S. Deering)
>
> o Review state/completeness of current IPv6-related protocols (B.
Hinden)
>
> - IPv6 Protocols
> o Base Protocol
> o Addressing
> o ICMP, Neighbor discovery, auto config, MLD
> o IPover<link>, Header compression
> o DNS
> o MIB's
> o Path MTU
> o Router Alert
> o Jumbograms
> - API's
> - Routing Protocols (Unicast and Multicast)
> - DHCP
> - IP Mobility
>
> o Identify important new IPv6 protocol/standards work
>
> - State of Plug-and-Play (B. Hinden)
> o "Dentist's office"
> o Secure "Dentist's office"
> - Securing ICMP/ND/MLD (S. Deering)
> - Will IPv6 work for a Billion (or more) PDA's and
> Mobile Phones? (B. Hinden)
> - Better Support for Multihomed Hosts (R. Draves)
> - Better Support for Multihomed Sites (E. Nordmark)
> - Privacy issues with use of EUI-64 IDs (T. Narten)
> - Source and Destination Address Selection (T. Narten)
> - Making TCP use Global Interface IDs (A. Mankin/T. Narten/M.
Crawford)
>
> (3) Formulate recommendations to the IESG/IAB, re future IPv6
> work (S. Deering, B. Hinden)
>
> - Disposition of IPng w.g. (extend charter? go on hiatus?)
> - Distribution of work to other existing WGs?
> - Evaluation of all IETF protocols for "IPv6-readiness"?
> - Recommendations for establishing new WG(s) or RG(s)?
>
>
>
>
>
>
>--------------------------------------------------------------------
>IETF IPng Working Group Mailing List
>IPng Home Page: http://playground.sun.com/ipng
>FTP archive: ftp://playground.sun.com/pub/ipng
>Direct all administrative requests to majordomo@localhost
>--------------------------------------------------------------------
>
|