IETF Logo Mail Archive

Re: [bess] AD Review of draft-ietf-bess-mvpn-bidir-ingress-replication-02

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Mon, 28 September 2015 14:51 UTC

Return-Path: <zzhang@juniper.net>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 208611ABD35; Mon, 28 Sep 2015 07:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.907
X-Spam-Level:
X-Spam-Status: No, score=-0.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FS_REPLICA=0.994, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 PDJWiilccBaU; Mon, 28 Sep 2015 07:51:51 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0128.outbound.protection.outlook.com [207.46.100.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 265EE1A9308; Mon, 28 Sep 2015 07:51:50 -0700 (PDT)
Received: from BLUPR0501MB1715.namprd05.prod.outlook.com (10.163.120.18) by BLUPR0501MB1714.namprd05.prod.outlook.com (10.163.120.17) with Microsoft SMTP Server (TLS) id 15.1.280.20; Mon, 28 Sep 2015 14:51:49 +0000
Received: from BLUPR0501MB1715.namprd05.prod.outlook.com ([10.163.120.18]) by BLUPR0501MB1715.namprd05.prod.outlook.com ([10.163.120.18]) with mapi id 15.01.0280.017; Mon, 28 Sep 2015 14:51:49 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "draft-ietf-bess-mvpn-bidir-ingress-replication@ietf.org" <draft-ietf-bess-mvpn-bidir-ingress-replication@ietf.org>
Thread-Topic: AD Review of draft-ietf-bess-mvpn-bidir-ingress-replication-02
Thread-Index: AQHQ9t5VHlD7dQG6Pkan2vK2cWbI755NhaEQgAAksYCABF2HkA==
Date: Mon, 28 Sep 2015 14:51:48 +0000
Message-ID: <BLUPR0501MB1715DE33950F8876C858D530D44F0@BLUPR0501MB1715.namprd05.prod.outlook.com>
References: <D2298FF9.D375F%aretana@cisco.com> <CY1PR0501MB17215852447D81D0406DAF42D4420@CY1PR0501MB1721.namprd05.prod.outlook.com> <D22B0FDE.D3B90%aretana@cisco.com>
In-Reply-To: <D22B0FDE.D3B90%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=zzhang@juniper.net;
x-originating-ip: [66.129.241.10]
x-microsoft-exchange-diagnostics: 1; BLUPR0501MB1714; 5:2N045WJ0wBtB5YAYA5tc+738QmNPHHrPgFBxnv9PdaQhay1wOQ1rLPRmxYpIDBPWPHDjXzirA3d9/jxdfU7O2iv8G3BWM889ry56mD3k9fWcOoYWaz+iwb6LXxZvW8GuCz3gMr6V+UgV7pZ9W1bU3w==; 24:IwIgimNCPOWTaVv5gmNTPK3kQjOvSxgKXeT+oCRDkAMswEo8BZusf7w9PyUtWYUc0df35F+1rQWw4eXrF8eLg/6VglUf6HN9Dh4RUGuI/gI=; 20:HkMsuc6aShuTmhvfs4NEmxxNIHdc3cRTmOYpbEdkHLFgegar5zTQPXY4y5R8+sHZ1kwCxIs3kpUwEqnunk4rNg==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0501MB1714;
x-ld-processed: bea78b3c-4cdb-4130-854a-1d193232e5f4,ExtAddr
x-microsoft-antispam-prvs: <BLUPR0501MB17141202C4EFEEDD47C21E5FD44F0@BLUPR0501MB1714.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(108003899814671);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(520078)(8121501046)(3002001); SRVR:BLUPR0501MB1714; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0501MB1714;
x-forefront-prvs: 0713BC207F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(199003)(189002)(122556002)(50986999)(40100003)(64706001)(106116001)(33656002)(106356001)(19625215002)(76176999)(66066001)(230783001)(19617315012)(101416001)(76576001)(74316001)(54356999)(5003600100002)(19609705001)(11100500001)(102836002)(5007970100001)(15975445007)(5001960100002)(19580395003)(5004730100002)(189998001)(19300405004)(77096005)(5002640100001)(81156007)(10400500002)(5001920100001)(5001860100001)(105586002)(16236675004)(99286002)(86362001)(46102003)(68736005)(5001830100001)(87936001)(4001540100001)(2900100001)(2950100001)(77156002)(97736004)(5001770100001)(92566002)(2501003)(62966003); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0501MB1714; H:BLUPR0501MB1715.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BLUPR0501MB1715DE33950F8876C858D530D44F0BLUPR0501MB1715_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Sep 2015 14:51:48.7357 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0501MB1714
Archived-At: <http://mailarchive.ietf.org/arch/msg/bess/3L64pUvVqiyFoLN6ODqou2BnsC0>
Cc: "EXT - thomas.morin@orange.com" <thomas.morin@orange.com>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Subject: Re: [bess] AD Review of draft-ietf-bess-mvpn-bidir-ingress-replication-02
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2015 14:51:55 -0000

Alvaro,
> I-D.ietf-bess-ir and I-D.ietf-bess-mvpn-extranet should be Normative References.
I thought about this further, and would like to keep them both as informational for the following reasons.
The extranet draft is referred to in the draft as following:
   ... The label may be shared
   with other P-tunnels, subject to the anti-ambiguity rules for
   extranet [I-D.ietf-bess-mvpn-extranet<https://tools.ietf.org/html/draft-ietf-bess-mvpn-bidir-ingress-replication-02#ref-I-D.ietf-bess-mvpn-extranet>].
Both extranet and label sharing are optional, not required for implementing the procedures in this draft.

As for draft-ietf-bess-ir: RFC 6514 specifies the use of IR P-tunnels, though there are some problems with RFC 6514's specification of IR P-tunnels, which are addressed in detail in draft-ietf-bess-ir.



Draft-ietf-bess-mvpn-bidir-ingress-replication explains how to support a VPN customer's use of BIDIR-PIM when the service provider uses IR P-tunnels, but it doesn't really depend on those details specified in draft-ietf-bess-ir. Thus draft-ietf-bess-ir should not be a normative reference for it.



Thanks!

Jeffrey

v2.23.0 | Report a Bug | By Email