Carrying Geo Coordinates in BGP
draft-chen-idr-geo-coordinates-02

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           E. Chen
Internet Draft                                                  N. Shen
Intended Status: Standards Track                          Cisco Systems
Expiration Date: April 29, 2017                               R. Raszuk
                                                           Bloomberg LP
                                                       October 28, 2016

                    Carrying Geo Coordinates in BGP
                 draft-chen-idr-geo-coordinates-02.txt

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/1id-abstracts.html

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

   This Internet-Draft will expire on April 29, 2017.

Copyright Notice

   Copyright (c) 2016 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. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Chen, Shen & Raszuk                                             [Page 1]

Internet Draft    draft-chen-idr-geo-coordinates-02.txt     October 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Abstract

   In this document we specify a new BGP capability - the Geo Coordinate
   Capability, and a new BGP attribute - the Geo Coordinate Attribute,
   for carrying the Geo Coordinate information in BGP.

1. Introduction

   There are several potential applications as described hereby for the
   physical location information of BGP speakers [RFC4271] in a network.

   In an "overlay network" without IGPs or where the "underlay network"
   belongs to a different administrative domain (e.g., using the BGP
   Tunnel Encapsulation Attribute [I-D.ietf-idr-tunnel-encaps]), the
   geographical location of the BGP speaker that sources the route in
   the network can be used to derive some rough sense of "distance" as a
   parameter in lieu of the IGP-metric in BGP path selection.

   In the applications of "Service Function Chaining" [RFC7665], the Geo
   location information of the Service Function Forwarders or the
   Service Nodes, can help the design of Service Function Paths with
   better traffic pattern and a lower latency.

   The knowledge of the physical location of BGP speakers can also be
   used to simplify the operational procedures for setting the outbound
   "MED" value in route advertisement.

   In this document we specify a new BGP capability - the Geo Coordinate
   Capability, and a new BGP attribute - the Geo Coordinate Attribute,
   for carrying the Geo Coordinate information in BGP.

1.1. Specification of Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Chen, Shen & Raszuk                                             [Page 2]

Internet Draft    draft-chen-idr-geo-coordinates-02.txt     October 2016

2. The Geo Coordinate Capability

   The Geo Coordinate Capability is a new BGP capability [RFC5492].  The
   Capability Code for this capability is specified in the "IANA
   Considerations" section of this document.  The Capability Length is
   20 octets.  The Capability Value consists of the following fields
   that specify the location of the speaker using the WGS-84 (World
   Geodetic System) reference coordinate system [WGS-84]:

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Show full document text