idnits 2.17.1 draft-michaelson-4byte-as-representation-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 118. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 184 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 6 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 2006) is 6343 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' Summary: 12 errors (**), 0 flaws (~~), 3 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group G. Michaelson 2 Request for Comments: DRAFT APNIC 3 Expires December 2006 5 Canonical representation of 4-byte AS numbers 7 draft-michaelson-4byte-as-representation-00.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Abstract 34 A single representation for 4-byte AS numbers is proposed, to avoid any 35 confusion in interpreting the two 2-byte quantities that make them. The 36 syntax chosen avoids collision with BGP community string parsing of AS 37 numbers. 39 It is recommended that only this representation be used by all documents 40 and systems referring to 4-byte AS numbers. 41 Nomenclature 43 1.0 Proposed canonical 4-byte AS representation 45 4 Byte AS numbers are defined in [1]. 47 It is proposed to identify 4-byte AS Numbers using a syntax of 48 .. 50 Accordingly, a 4-byte AS Number of value 65546 (decimal) would be 51 identified as "1.10". 53 2.0 Terminology 55 "2-byte only AS Numbers" refers to AS Numbers in the range 0 - 65535 57 "4-byte only AS Numbers" refers to AS Numbers in the range 1.0 - 58 65535.65535 (decimal range 65,536 - 4,294,967,295) 60 "4-byte AS Numbers" refers to AS Numbers in the range 0.0 - 65535.65535 61 (decimal range 0 - 4,294,967,295) 63 3.0 Discussion 65 To avoid confusion, a single notation to represent 4-byte AS is 66 required. Initially, the ":" was proposed to separate the 2-byte 67 components. However this clashes with use of the ":" character in 68 community attribute syntax. 70 This notation has been informally adopted by at least one vendor, and 71 used consistently in presentations in the RIR community towards the 72 deployment of 4-byte AS. Therefore it seems sensible to formalize its 73 use as the preferred representation of a 4-byte AS. 75 4.0 Author's Note: 77 This proposal was motivated by a discussion with Geoff Huston. The 78 text of the definition of a 4-byte AS is taken from [2]. 80 5.0 Security Considerations 82 Security considerations are not discussed in this memo. 84 6.0 Author's Address: 86 George Michaelson 87 APNIC 88 Level 1, 33 Park Road, Milton, Q4064 Australia 90 7.0 References 92 [1] http://www1.ietf.org/internet-drafts/draft-ietf-idr-as4bytes-12.txt 93 [2] http://www.ripe.net/ripe/policies/proposals/2005-12.html 95 8.0 Comments & Feedback 97 Comments are solicited and should be addressed to the working group's 98 mailing list at idr@ietf.org and/or the author. 100 9.0 Authors email address 102 ggm@apnic.net 104 10.0 Copyright Declaration 106 Copyright (C) The Internet Society (2006). 108 This document is subject to the rights, licenses and restrictions 109 contained in BCP 78, and except as set forth therein, the authors retain 110 all their rights." 112 "This document and the information contained herein are provided on an 113 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 114 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 115 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 116 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 117 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 118 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.