IETF Logo Mail Archive

Re: [Bier] BIER WGLC: draft-ietf-bier-php

"Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com> Fri, 27 September 2019 11:19 UTC

Return-Path: <naikumar@cisco.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18324120805; Fri, 27 Sep 2019 04:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=OA4Rnt+F; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=CKUyoeWd
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 EmYFWe6Qs-xq; Fri, 27 Sep 2019 04:19:06 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD3F7120801; Fri, 27 Sep 2019 04:19:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12461; q=dns/txt; s=iport; t=1569583146; x=1570792746; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Myzg7X6C6ZBVQmmuZ4wakNPM5M5FpSvGW8saXeWbnV0=; b=OA4Rnt+FjhuViHYGkk/AzwkPxenNyQTe/YVv+LSY4W/fuUb3hox/xZ42 X/L95zpq/EPN+mQFGbrnMsgN+5Yq4dQzSEPt1PZ9k0ZpuAbmRU/tcAAh4 d/yc4XpQqx8uVrg01JKB69Jq3LFp3gZsCOWR76FAq9+/XHlblBzjZfbfX U=;
IronPort-PHdr: 9a23:yqTg9x+r0o0EPf9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVciMCE7mKffwRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHAABw741d/4wNJK1mGQEBAQEBAQEBAQEBAQwBAQEBAQGBUwQBAQEBAQsBgRsvUANtViAECyoKhBiDRwOEUoYGgjcliWeJMIRfgS6BJANUCQEBAQwBASMKAgEBhEACF4MgIzQJDgIDCQEBBAEBAQIBBQRthS0MhUsBAQEEEhEdAQE3AQ8CAQgRAwECKAMCAgIfERQJCAIEAQ0FIoMAAYEdTQMdAQ6ibAKBOIhhc4Eygn0BAQWBR0FAgkcNC4IXAwaBNAGMCxiBf4ERJwwTgkw+ghpHAgMBgX0NCYJVMoImj1yFLYkojihBCoIihwWKBIQCG4I3h0yEKosHjiGIF4IKjn0CBAIEBQIOAQEFgVI4gVhwFWUBgkFQEBSBToNyhRSFP3SBKYx3AYEiAQE
X-IronPort-AV: E=Sophos;i="5.64,555,1559520000"; d="scan'208,217";a="637933844"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Sep 2019 11:19:05 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by alln-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x8RBJ5BF022568 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 27 Sep 2019 11:19:05 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 27 Sep 2019 06:19:04 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 27 Sep 2019 06:19:04 -0500
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 27 Sep 2019 06:19:04 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Q9xGzwI7Ak/WnJJKpPG2NlKQ64JWKHKznPSnnZKNHmMmw55yMbzL8RcJwY+LSXV5Tk+aO9ruV2yQsRqJZPTqpILcTmYJr5U1imvuMycU3xOQPZ4PFuOhWWcdbC/CTLLdwME28lB0kf5map33GJvCaQuZG/aj5okzpj4raCqP4vi183Ig9I+GvCqoQDlETyZmeLLslcOnEKE3oVXnHbQe2m7XEVyHMwkZlGw9ilHnWl54yWDJxIJVj+xvWPUSNEcDLEfoMvkSWlDBg7QiZgXeQKz0ST3NyGXA2I6t24St6pR7LgZMCX3FOODG33NMun6Pp3D9brvraolxgh/D5drg3A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Myzg7X6C6ZBVQmmuZ4wakNPM5M5FpSvGW8saXeWbnV0=; b=GGL8CbDzlOlY3HdqvB2+6YbUGqJFaLHg+q5sNc8j+AvN/1FYjrb3Ko9jiRmc01dA7oUQ6bFymb5tlsPNdcczaJLIxufE1X3BPobdm4BCWdvmRJ1+50XOMEEF1j1FvbyzxZO/daGtrbISC09uspk+JW17MREF+E17iTnF3D06NwtHuPd+OTcAkfo+R5Ih1GuePwwraXCb6HLSLX3iq6HDHVq0qWGU3leupQ9JLoIr3pmlmu+Uz3e50Fti/xnGkzoCMFIMePcIHruDkMu1jgW4eCAIDc8/Hlts3zW/QRHcCwZGPXclCnrGntJfbMcdzbizUiIxIK7KaXno4HUm3cjssQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Myzg7X6C6ZBVQmmuZ4wakNPM5M5FpSvGW8saXeWbnV0=; b=CKUyoeWdHmqKh1OMq7fIUx4SwiBsV7vQYtmpeQL7bLVJBoLxlrhjsslTghGtvxoRE+7/VCvBMaAoCN1SChVK62ujU0SA2dmWVky+LWYdP5U76HjCUiYQbN6nfLmZmDgCLg+2g/F3UksA9NsauT2WfI81PTvWk1TMkFO4ja47AsA=
Received: from BN6PR11MB4145.namprd11.prod.outlook.com (10.255.129.84) by BN6PR11MB1539.namprd11.prod.outlook.com (10.172.23.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.19; Fri, 27 Sep 2019 11:19:03 +0000
Received: from BN6PR11MB4145.namprd11.prod.outlook.com ([fe80::dd1c:48d9:86bd:8995]) by BN6PR11MB4145.namprd11.prod.outlook.com ([fe80::dd1c:48d9:86bd:8995%7]) with mapi id 15.20.2284.028; Fri, 27 Sep 2019 11:19:03 +0000
From: "Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com>
To: "gjshep@gmail.com" <gjshep@gmail.com>, BIER WG <bier@ietf.org>
CC: "draft-ietf-bier-php@ietf.org" <draft-ietf-bier-php@ietf.org>
Thread-Topic: [Bier] BIER WGLC: draft-ietf-bier-php
Thread-Index: AQHVRwP/N+kcxww5okevlmjRYwOp3qc1ZMuAgAmOzgA=
Date: Fri, 27 Sep 2019 11:19:03 +0000
Message-ID: <89429DD1-EB74-4641-A222-3522770DD471@cisco.com>
References: <CABFReBrqzdz1wbK_weeQD05LfrDZbSsfroj46ecpfWDiBoX2Qw@mail.gmail.com> <CABFReBp=n9KgS4ipkWvxAKdc5ciX6ej+=aZJzhUTGyQyTArdsQ@mail.gmail.com>
In-Reply-To: <CABFReBp=n9KgS4ipkWvxAKdc5ciX6ej+=aZJzhUTGyQyTArdsQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.d.190811
authentication-results: spf=none (sender IP is ) smtp.mailfrom=naikumar@cisco.com;
x-originating-ip: [173.38.117.85]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a0749b48-6253-4f99-f945-08d7433c80a7
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BN6PR11MB1539;
x-ms-traffictypediagnostic: BN6PR11MB1539:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BN6PR11MB1539A43E01E2EF292B2CE005C6810@BN6PR11MB1539.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0173C6D4D5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(376002)(136003)(396003)(39860400002)(346002)(189003)(199004)(6436002)(606006)(25786009)(966005)(71190400001)(66476007)(316002)(6506007)(6116002)(76176011)(186003)(6486002)(99286004)(4326008)(66556008)(91956017)(66946007)(3846002)(64756008)(256004)(102836004)(76116006)(26005)(2501003)(58126008)(476003)(53546011)(446003)(110136005)(486006)(11346002)(2616005)(66066001)(6306002)(66446008)(36756003)(2906002)(66574012)(14444005)(71200400001)(7736002)(86362001)(6512007)(236005)(81156014)(54896002)(14454004)(5660300002)(8936002)(8676002)(6246003)(33656002)(229853002)(478600001)(81166006)(24704002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR11MB1539; H:BN6PR11MB4145.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: s7Z9A/OJjdw+1TQGbe2xveL3X9v5a9Ektw/8UxAYJv+d7Bhgn0B+zf/hCkfccn/w8fGf2uCPkFUwvFUADZjOnregHCn2+HVvHLLTXs3PNMWjiKU0IrAlLgBQ9mQwf0CJvR4TMsPu+TiF1ZANnritsMtg+s2pr15FvOQh5LIq+/kgF0SZ/WBnKItrjjePvp6G3iEqQbyxCKw65rUypXZKjqYeBLGkmDl7XG2vPIwCKfo0Eu57uXF02rFChhB7fR1wOxJ+bOSOO9LSqqbIKWhqJhw9by9Z/kVYtRlo7EllSAmnWhFA2tQ1nNtTlyudgfYvDsE19CUXaWjDrjZaI7mx1e3l+aM3VEMUTQDlCadPFb7qXzbzJ+YYUIu39/dkTdJ0hPN+5xACUmQ2LOQZqEilXOUsxnQ03pSqvMBXOb4LWYUISmbVg0hgAQLrku6EEcsfI+3FKFo502e5wfa6xKWvqA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_89429DD1EB744641A2223522770DD471ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a0749b48-6253-4f99-f945-08d7433c80a7
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Sep 2019 11:19:03.1095 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: yuxKtDjDHSo72dBlSAY+g5eCoNdRackqZT6fblBL2IyaG/39iLZqHsKfI9sufXI+wOKA9pIzCfJF8uEDnyTZPQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1539
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xch-rcd-012.cisco.com
X-Outbound-Node: alln-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/HSi97OuxQCa8WrX0w0hXBwqMUW0>
Subject: Re: [Bier] BIER WGLC: draft-ietf-bier-php
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 11:19:09 -0000

Hi,

Support.

I have a couple of comments as below:


  1.  Based on the Introduction section, the upstream BFR that pops the BIER header can be directly to PE (BIER incapable) or through a tunnel. In case of non-directly connected BFR, Is it really “PHP” or is it BIER to LSP stitching?.
  2.  In addition to the assumption/limitation mentioned in the start of Section 3, I think this draft assumes the presence of LSP tunnel between the upstream BFR and BIER-incapable PE. If it is non-MPLS network, does it expect to encapsulate with IP/UDP?. Either way, I think it is better to clarify the same in the draft.
  3.  The introduction says the below:
“
While the above text uses MVPN/EVPN as example, BIER PHP is
   applicable to any scenario where the multicast flow overlay edge
   router does not support BIER.”

The above appears to contradict with section 3 that says, BIER PHP is applicable only when BIER NH =1.

Regards,
Nagendra

From: BIER <bier-bounces@ietf.org> on behalf of Greg Shepherd <gjshep@gmail.com>
Reply-To: "gjshep@gmail.com" <gjshep@gmail.com>
Date: Friday, September 20, 2019 at 5:22 PM
To: BIER WG <bier@ietf.org>
Subject: Re: [Bier] BIER WGLC: draft-ietf-bier-php

We're long past Aug 13th and not one response. PLEASE read and respond or we'll just let this expire.

Thanks,
Greg

On Tue, Jul 30, 2019 at 11:23 AM Greg Shepherd <gjshep@gmail.com<mailto:gjshep@gmail.com>> wrote:
Please read and respond to this thread:

https://datatracker.ietf.org/doc/draft-ietf-bier-php/

EOTWT: Aug 13th.

Thanks,
Shep
(chairs)

v2.23.0 | Report a Bug | By Email