idnits 2.17.1 draft-manning-bgpattrib-type-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-23) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == 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 85 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** 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.) ** There are 2 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There are 17 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 11 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Bill Manning 2 April 1996 ISI 3 Expires in six months 5 How new BGP Attribute Types are defined 6 draft-manning-bgpattrib-type-00.txt 8 Status of this Memo 10 This document wants to be an Internet-Draft. Internet-Drafts are working 11 documents of the Internet Engineering Task Force (IETF), its areas, 12 and its working groups. Note that other groups may also distribute 13 working documents as Internet-Drafts. 15 Internet-Drafts are draft documents valid for a maximum of six months 16 and may be updated, replaced, or obsoleted by other documents at any 17 time. It is inappropriate to use Internet- Drafts as reference 18 material or to cite them other than as ``work in progress.'' 20 To learn the current status of any Internet-Draft, please check the 21 ``1id-abstracts.txt'' listing contained in the Internet- Drafts 22 Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net 23 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 24 Rim). 26 Process: 28 This document describes the process for creating new BGP attribute 29 type codes. Basic attribute type codes are described in RFC1771 30 pages 12 through 15. These, and new attribute type codes that are 31 used in the internet are expected to be registered with the IANA. 33 It is expected that new BGP attribute type codes will be registered 34 in a similar way that DNS RR's and SNMP subtypes are registered. 35 The actual process will involve the documentation of such attribute 36 type codes in FYI RFCs. There is no intention of segmenting the 37 code space into public/private or IP/OSI or any other sectioning. 39 As each attribute type code is in the process of being developed, it 40 will use an octect value of 255, which will be reserved for this use. 41 At the time an attribute type code is assigned a number by the IANA, 42 the documetnation and code base will be updated to reflect the 43 authorized attribute type code value. 45 IANA maintained values will be published in the periodically updated 46 assigned numbers STD. The bgp attribute type code list or pointer to 47 the bgp attribute type code list will be added to this STD. Requests 48 for assignment of a new attribute type code should be sent to IANA 49 with a subject that includes the phrase "attribute type code request". 51 Currently in use attribute type codes are listed below: 53 1 origin 54 2 as path 55 3 next hop 56 4 multi exit disc. 57 5 local preference 58 6 atomic aggregate 59 7 aggregator 60 8 community cisco ID 61 9 originator cisco ID 62 10 cluster list cisco ID 63 11 destination preference MCI ID 64 12 advertiser Bay ID 65 13 rcid_path (cluster id) Bay ID 66 ... 67 255 reserved for development 69 Security considerations of this memo 71 None. 73 Authors' Addresses 75 Bill Manning 76 USC/ISI 77 4676 Admiralty Way 78 Marina del Rey, CA. 90292 79 01.310.822.1511 80 bmanning@isi.edu