Re: [Idr] Questions to RFC5512: Encapsulation sub-TLV and Opaque extended community to indicate the Encapsulation protocol?

Linda Dunbar <linda.dunbar@huawei.com> Tue, 26 June 2018 18:03 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61701310ED for <idr@ietfa.amsl.com>; Tue, 26 Jun 2018 11:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.644
X-Spam-Level:
X-Spam-Status: No, score=-3.644 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_04=0.556, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id liUsjGU15kI3 for <idr@ietfa.amsl.com>; Tue, 26 Jun 2018 11:03:09 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41A221310EB for <idr@ietf.org>; Tue, 26 Jun 2018 11:03:08 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 81410F6584771 for <idr@ietf.org>; Tue, 26 Jun 2018 19:03:04 +0100 (IST)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 26 Jun 2018 19:03:05 +0100
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.90]) by SJCEML702-CHM.china.huawei.com ([169.254.4.125]) with mapi id 14.03.0382.000; Tue, 26 Jun 2018 11:02:57 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "idr@ietf.org" <idr@ietf.org>, "pmohapat@cisco.com" <pmohapat@cisco.com>, "erosen@cisco.com" <erosen@cisco.com>
Thread-Topic: [Idr] Questions to RFC5512: Encapsulation sub-TLV and Opaque extended community to indicate the Encapsulation protocol?
Thread-Index: AdQNcvGsoubNaEyuRiefKbIQXngA6QABOFGQ
Date: Tue, 26 Jun 2018 18:02:56 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B073A83@sjceml521-mbs.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B073A42@sjceml521-mbs.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B073A42@sjceml521-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.89]
Content-Type: multipart/related; boundary="_005_4A95BA014132FF49AE685FAB4B9F17F66B073A83sjceml521mbschi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/n1lIRSMotkGksjbzCwbk-eD5MGU>
Subject: Re: [Idr] Questions to RFC5512: Encapsulation sub-TLV and Opaque extended community to indicate the Encapsulation protocol?
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2018 18:03:11 -0000

BGP experts:

The RFC5512 has "distinguished SAFI value" and "the Encapsulation SAFI". Do those two terms have the same meaning?
The Section 3 of RFC5512 has SAFI value of 7 to represent Encapsulation SAFI.
Does it mean that the "distinguished SAFI value" is just "7" for speaker to advertise its supported Tunnel information?


The Section 4 goes on defining the Tunnel Encapsulation Type (such as L2TPv3 with Type =1; etc), and a list of sub-TLVs, one of the SubTLV is Protocol Type (section 4.2) which can be used to represent the Encapsulation Protocol (i.e. protocol type of data frames carried by the tunnel)

Why need the Opaque extended community to indicate the Encapsulation protocol?

[cid:image001.png@01D40D4D.FF829DA0]

[cid:image002.png@01D40D4D.FF829DA0]


Thank you very much.

Linda Dunbar