Internet Engineering Task Force                               J. Scudder
Internet-Draft                                          Juniper Networks
Intended status: Informational                         December 16, 2008
Expires: June 19, 2009


                    Registry for BGP-4 OPEN Options
                   draft-scudder-idr-open-registry-00

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on June 19, 2009.

Copyright Notice

   Copyright (c) 2008 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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.

Abstract

   The base BGP specification specifies a mechanism to include optional
   parameters with the OPEN message.  Optional parameters are identified



Scudder                   Expires June 19, 2009                 [Page 1]

Internet-Draft            OPEN Option Registry             December 2008


   by a type code.  However, no IANA registry exists for this type code.
   This document requests IANA to create such a registry.


.  Introduction

   The base BGP specification [RFC4271] specifies in Section 4.2 a
   mechanism to include optional parameters with the OPEN message.
   Optional parameters are identified by the Parameter Type, which is a
   one-octet unsigned binary integer.

   Two Parameter Type codes are currently defined:

   o  Parameter Type 1: Authentication (deprecated).

   o  Parameter Type 2: Capabilities ([RFC3392])

   This document requests that IANA create and maintain a registry for
   OPEN message optional parameters.


.  Acknowledgements

   Elwyn Davies pointed out that a registry for OPEN Options was needed.


.  IANA Considerations

   This document requests that IANA create and maintain a registry for
   "BGP OPEN Optional Parameter Type", as discussed above.  Values are
   to be allocated according to the "IETF Consensus" policy as defined
   in [RFC5226].


.  Security Considerations

   This document introduces no security issues.


.  Normative References

   [RFC3392]  Chandra, R. and J. Scudder, "Capabilities Advertisement
              with BGP-4", RFC 3392, November 2002.

   [RFC4271]  Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
              Protocol 4 (BGP-4)", RFC 4271, January 2006.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an



Scudder                   Expires June 19, 2009                 [Page 2]

Internet-Draft            OPEN Option Registry             December 2008


              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008.


Author's Address

   John Scudder
   Juniper Networks
   1194 N. Mathilda Ave
   Sunnyvale, CA  94089
   USA

   Email: jgs@juniper.net






































Scudder                   Expires June 19, 2009                 [Page 3]