ASN Label Switching Protocol (ALSP) Specification
draft-omar-alsp-00

Document Type Active Internet-Draft (individual)
Last updated 2020-04-16
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized 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)
draft-omar-alsp-00                                      Khaled Omar
Internet-Draft                                           The Road                                       
Intended status: Standard Track
Expires: October 16, 2020                             April 16, 2020                                       

                     ASN Label Switching Protocol (ALSP)
                             Specification
                           draft-omar-alsp-00

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering Task
   Force (IETF). Note that other groups may also distribute working documents
   as Internet-Drafts. The list of current Internet-Drafts is at
   http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on October 16, 2020.

Copyright Notice

   Copyright (c) 2020 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 the Trust Legal
   Provisions and are provided without warranty as described in the Simplified
   BSD License.

Abstract

   This document specifies ASN Label Switching Protocol (ALSP).

Table of Contents

   1. Introduction..................................................1
   2. ALSP Header...................................................1
   3. ASN Label Switching Protocol (ALSP)...........................1
   4. Security Considerations.......................................3
   5. Acknowledgments...............................................3
   6. Author Address................................................3
   7. References....................................................3
   8. Full Copyright Statement......................................3

Khaled Omar             Internet-Draft                   [Page 1]

RFC            ASN Label Switching Protocol (ALSP)   April 16, 2020

1.  Introduction

    - ASN Label Switching Protocol (ALSP) is a wide-area network (WAN)
      protocol that is used to connect an Enterprise's local-area networks
      (LANs) through Service Provider's network.
    - ALSP can be used to connect different Enterpises' networks as well
      that uses overlapped private IPv4 addresses.
    - ALSP depends on the unique ASN assigned to each organization.
    - ALSP is similar to the MPLS concept but much more simpler.  

2.  ALSP Header

  - ALSP adds the following header to the IP packet:

                  +-+-+-+-+-+-+
                  |    ASN    |
                  +-+-+-+-+-+-+
                     32-bits

 - ASN is the Autonomous System Number.

3.  ASN Label Switching Protocol (ALSP)

    - Consider the following two enterprise sites that are connected
      through an ALSP Cloud of routers:

  Customer-A                 SP-1                  Customer-A
    Site-1                ALSP Colud                Site-2
    ASN-100                 ASN-300                 ASN-100 
  
 *************          ****************          *************
 *10.1.1.0/24*          *              *          *           *
 *           *CE1    PE1*              *PE2    CE2*           *
 *   IGP-1 * x *o----o* x *  IGP-2   * x *o----o* x *  IGP-3  *
 *           *   eBGP   *              *   eBGP   *           *
 *           *          *              *          *           *
 *************          ****************          *************

    Sample Network for Connecting an Enterprise with Two Sites

Where:

  - CE: Customer Edge.
  - PE: Provider Edge.
  - ASN: Autonomous System Number.
  - IGP: Interior Gateway Protocol.
  - eBGP: External Boarder Gateway Protocol.  

  - CE1 has ALSP enabled on the interface connected to PE1.
  - Similarly, CE2 has ALSP enabled on the interface connected
    to PE2.
  - Also, all the ALSP cloud routers have ALSP enabled globally.
  - ALSP enabled interface means that the IGP or EGP advertisements
    through this interface can have the ALSP header which is the ASN
    configured on the IGP or EGP.
  - Consider that Customer-A's Site-1 has a subnet 10.1.1.0/24 that
    needs to be advertised to Site-2.
Show full document text