Transcript PPT Version
ITU Liaison IS-IS for IP Standardization Request Jonathan Sadler SG15 Liaison to IETF for Routing http://intwww/~jsadler/routing.ppt Background ITU SG15 Standardizes Transport Equipment G.707 – SDH/SONET G.709 – Digital Wrapper Q14/15 is responsible for Standardizing Management G.7712 - ARCHITECTURE AND SPECIFICATION OF DATA COMMUNICATION NETWORK Standardized in Oct 2001, v2 in Jan 2003 Extends Management Network defined in Q.811 Adds Signaling Communications Network (SCN) Adds support for IP over the SONET/SDH DCC, G.709 GCC via PPP IS-IS defined for use in IP and OSI MCN/SCN April 24, 2002-#2 http://intwww/~jsadler/routing.ppt ITU Citation Rules for RFCs (Rec. A.5) Based on RFC 2026 Sec. 4 “An "Informational" specification is published for the general information of the Internet community, and does not represent an Internet community consensus or recommendation. The Informational designation is intended to provide for the timely publication of a very broad range of responsible informational documents from many sources, subject only to editorial considerations and to verification that there has been adequate coordination with the standards process (see section 4.2.3). “Specifications that have been prepared outside of the Internet community and are not incorporated into the Internet Standards Process by any of the provisions of section 10 may be published as Informational RFCs, with the permission of the owner and the concurrence of the RFC Editor.” Normative References can only be made docs of status: Best Current Practice Proposed Standard Draft Standard Internet Standard April 24, 2002-#3 http://intwww/~jsadler/routing.ppt IS-IS for IP Two Technical Issues IS-IS Hellos on an Unreliable Data Link (i.e. PPP) Addressed with Three-Way Handshake (RFC 3373) Domain-wide Prefix Distribution (RFC 2966) April 24, 2002-#4 http://intwww/~jsadler/routing.ppt The Problem Can’t cite as normative text due to Informational Status Can’t copy into G.7712 due to IETF copyright Temporarily Resolved by Paraphrasing Text However, paraphrasing can cause further problems April 24, 2002-#5 http://intwww/~jsadler/routing.ppt The Proper Solution With the agreement between IETF and JTC1 re: IS-IS Standardization: Internet-specific IS-IS Extensions can become Standards Track RFCs without JTC1 involvement Core IS-IS Mechanisms Extensions can be submitted to JTC1 for Fast-Track review/approval RFC 2966 falls under “Internet-specific IS-IS Extensions” No modification to code IS-IS Mechanisms Could be reclassified as Standards Track without JTC1 RFC 3373 falls under IS-IS Mechanisms Extensions Modifies adjacency state machine and formation logic April 24, 2002-#6 http://intwww/~jsadler/routing.ppt The Request Liaison from ITU-T Q14/15: “We request that the IS-IS Working Group give priority consideration for the reclassification of the following RFC: RFC 2966 - Domain-wide Prefix Distribution with Two-Level IS-IS Further, we request that the IS-IS Working Group submit the following RFC to JTC1 for processing under the ISO/IEC Fasttrack approval process: RFC 3373 - Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point Adjacencies We appreciate your attention to this matter.” Liaison can be found at: ftp://sg15opticalt:[email protected]/tsg15opticaltransport/COMMUNICATIONS/index.html April 24, 2002-#7 http://intwww/~jsadler/routing.ppt