IETF REPORT RIPE Meeting Amsterdam, The Netherlands January 25 - 27, 1995 Joyce K. Reynolds Information Sciences Institute University of Southern California Marina del Rey, California USA jkrey@isi.edu IETF REPORT San Jose IETF Stats IPng Area HTTP BOF/SGML WG IIIA - IAB Retreat User Services Area IETF REPORT San Jose IETF Stats 1107 Total Attendees From the Multicast side: 710 hosts from 25 countries 77 Groups met (This includes WGs, BOFs, Directorates, and the IAB) [Some in multiple sessions.] IETF REPORT IPng Co-Area Directors: Allison Mankin Scott Bradner Topics: -Addressing Plan -Autoconfiguration -Security -European Perspective -Related WGs & BOFs -Suggested Reading IETF REPORT IPng Area - Comments on IPv4 Addressing - Changes in address assignment policies are not recommended. - Reclamation of underutilized assigned addresses is not currently recommended. - Efforts to renumber significant portions of the Internet is not currently recommended. - Recommend consideration of assigning CIDR-type address blocks out of unassigned Class A addresses. IETF REPORT IPng Area - Addressing Plan - hotly discussed issue - four basic views: - 8 bytes is enough, more is inefficient - 16 bytes is about right, 8 is not enough - use 20 byte NSAPs, provide global harmonization - variable length gives best safety and efficiency - many detailed arguments - consensus is that expansion to 16 byte address space is enough IETF REPORT IPng Area-Autoconfiguration - Transparent address (plug & play) - Security considerations - Formation of an Address Autoconfiguration WG (addrconf) to focus on the allocation of dynamic addresses to IPng hosts. IETF REPORT IPng Area - Security Recommendations: - Support for the Authorization Header be required. - Support for a specific authentication algorithm be required. - Support for the Privacy Header be required. - Support for a specific privacy algorithm be required. - ``IPng Framework for Firewalls" be developed. IETF REPORT IPng Co-Area Directors' Thoughts on the European Perspective Security: - Security requirements should not be hindered by patent rights in Europe (or elsewhere). - Interested in encouraging European activism in deploying secure IPng. - Comparable to European Unix Crypto Algorithm Competition. IETF REPORT IPng Co-Area Directors' Thoughts on the European Perspective Address Architecture: - Modified for Europe due to widely accepted provider-based addressing. - Geography/Provider match may change. - Set a context for provider planning now. IETF REPORT IPng Transition - Proposed WGs IPng Transition Chairs: Ross Callon, Steve Deering Document Editor: Bob Hinden Goals: Resolve any remaining issues. Cooperate with work in other areas impacted by IPng. IETF REPORT IPng Transition - Proposed WGs AUTOCONF Chairs: Sue Thomson and Dave Katz Goals: short term Working Group focus on documents for server-less and stateless-server modes of address autoconfiguration DHCP done in DHCP WG coordinate with other IETF activities affected by autoconfiguration such as CNS (for autoregistration) and CAT (for authentication) IETF REPORT IPng Transition - Proposed WGs Two IPng transition efforts: short term - refine IPng-specific documents for proposed standard long term - transition, coexistence and testing work together IETF REPORT IPng Transition - Proposed WGs NGTRANS Chair: Bob Gilligan Goals: short term Working Group focus on IPng transition and coexistence work with TACIT WG finalize IPng transition overview develop documents relating directly to the IPng transition IETF REPORT IPng Transition - Proposed WGs TACIT Chairs: TBA Goals: long term Working Group learn from other transition and deployment efforts detail problem areas in transition and coexistence facilitate transition plans from other network technologies (e.g., IPX, CLNP) IETF REPORT IPng Transition - Proposed WGs TACIT Goals (Continued): recommendation of specific testing procedures recommendation of coexistence operations procedures with IPv4 recommendations for the smoothing of decentralized transition planning IETF REPORT IPng Transition - Proposed WGs NOSI Chair: Brian Carpenter Items to persue: RFC 1006bis (ISO transport over TCP, small modifications to existing RFC) Classic CLNP over IPng tunnels (NextHeader = CLNP; probably no new document needed, at most a very short RFC) TP4 over IPng (requires some real work, volunteer needed) IETF REPORT IPng Reviewer Appointment of an IPng reviewer specifically responsible for ensuring that a conssitent view of IPng is maintained accross related WGs. Needed since IPng related work will be going on in a number of IETF areas. Job is long term, offering broadest perspective. Must be able to question, connect all the efforts, spot gaps and misunderstandings, but not making architectural decisions Dave Clark IETF REPORT IPng Area - Suggested Reading RFC 1752 ``The Recommendation for the IP Next Generation Protocol" URL: ftp://ftp.ripe.net/rfc/rfc1752.txt RFC 1636 ``Report of IAB Workshop on Security in the Internet Architecture February 8-10, 1994" URL: ftp://ftp.ripe.net/rfc/rfc1636.txt IETF REPORT HTTP BOF/SGML WG - HTTP BOF - MIMESGML WG IIIA - IAB Retreat Report to be published. IETF REPORT User Services Area - not end-user specific area - second level service - HTMLing FYI RFC series - USV-WEB - Bringing in other disciplines - New WGs - Liase with TERENA ISUS and RIPE NIDUS - More detail in NIDUS session IETF REPORT Acknowledgements Paul Mockapetris Steve Coya Allison Mankin Scott Bradner Jon Postel ============================================= Second talk: The User Services Area of the IETF RIPE Meeting Amsterdam, The Netherlands January 25 - 27, 1995 Joyce K. Reynolds Information Sciences Institute University of Southern California Marina del Rey, California USA jkrey@isi.edu The User Services Area of the IETF - Started in 1989 as one Working Group within the IETF (USWG). - January 1991 - User Services Area (USV) created. - Currently, we have 11 WGs. The User Services Area of the IETF - International in scope. - Interact and liase with other global organizations (e.g., TERENA, RIPE, CNI, APNIC, etc.) The User Services Area of the IETF - IETF User Services Area is a second level service. - We are NOT an end-user specific entity. - ALL levels of users, not just novice. The User Services Area of the IETF - User, Information, and Network Services. - Act as a neutral point for NICs of all levels (local, regional, global) to participate in the IETF forum to exchange ideas. The User Services Area of the IETF - We interact with other Areas in the IETF (e.g., Applications, Operations, Security, etc.). - Interact with other disciplines (e.g., Librarians, School Teachers, etc.) IETF User Services Working Groups and Projects *Integrated Directory Services (IDS) *Integration of Internet Information Resources (IIIR) Internet School Networking (ISN) Network Information Services Infrastructure (NISI) *Joint APP/USV effort IETF User Services Working Groups and Projects Network Training Materials (TRAINMAT) [IETF/TERENA endeavor] Responsible Use of the Network (RUN) *Quality of Information Services (QUIS) *Joint APP/USV effort IETF User Services Working Groups and Projects **Site Security Handbook (SSH) *Universal Resource Identifiers (URI) User Services (USWG) *Whois and Network Information Lookup Services (WNILS) *Joint APP/USV effort **Joint SEC/USV effort IETF User Services Working Groups and Projects Arts and Humanites - Sharing Center Stage on the Internet (ARTS) BOF *Referral Whois Protocol (RWHOIS) BOF User Services Area Council (USAC) *Joint OPS/APP/USV effort The User Services Area of the IETF - The FYI RFC Series of Notes. Currently, 27 FYI RFCs. Handbooks, Catalogues, Glossaries, etc. For example, Site Security Handbook, Internet Users' Glossary, NOCTools Catalogue, etc.