IETF Logo Mail Archive

Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext – [4/18 – 5/2] - extended to 5/9

reta Yang <reta.yang@outlook.com> Mon, 06 May 2019 00:58 UTC

Return-Path: <reta.yang@outlook.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 5A9501200EC for <idr@ietfa.amsl.com>; Sun, 5 May 2019 17:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.com
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 p2TeRxiUUMrJ for <idr@ietfa.amsl.com>; Sun, 5 May 2019 17:58:03 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-oln040092253082.outbound.protection.outlook.com [40.92.253.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FAD51205DE for <idr@ietf.org>; Sun, 5 May 2019 17:56:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ifuL5Uwd6PZu7NPA/h0EP0Tjb7P5H3P93nIzJz9wwYo=; b=lD2HOQsyHFNycA8tQMdrFe+GfKFIdjaqsk2Fa3g92QEPpY2nkKcN4bHXHP8n5v9KWYENtsw6B+33Md6WJhzoURrUCe1OnZYKnWUS7h/GsKTCoMoRLlHgyGmdbj6qakTBlNTrEvw6KUkWft+F1FugGs4G6ZCwv38KK4C2vWk1Ypo+atprCu1uQ8hpEgWhlUiVsAO+VwUQR1PR3D2E7ndJQeoSEriO/BgWA2mAk463bcbaX/mU8XJgfJ1bvOKQxA9jDHJxtClrJnp1sHtn7z4k2+tnwF1FJcJvoJB364TGHACk42uknuwdq8x9wnsULtXwPiKTnWlLtCaR/yDRAJeNAQ==
Received: from SG2APC01FT058.eop-APC01.prod.protection.outlook.com (10.152.250.51) by SG2APC01HT079.eop-APC01.prod.protection.outlook.com (10.152.251.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1856.11; Mon, 6 May 2019 00:56:09 +0000
Received: from SG2PR06MB3176.apcprd06.prod.outlook.com (10.152.250.54) by SG2APC01FT058.mail.protection.outlook.com (10.152.251.117) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1856.11 via Frontend Transport; Mon, 6 May 2019 00:56:09 +0000
Received: from SG2PR06MB3176.apcprd06.prod.outlook.com ([fe80::7548:3d1e:7578:d684]) by SG2PR06MB3176.apcprd06.prod.outlook.com ([fe80::7548:3d1e:7578:d684%5]) with mapi id 15.20.1856.012; Mon, 6 May 2019 00:56:09 +0000
From: reta Yang <reta.yang@outlook.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] draft-wu-idr-bgp-segment-allocation-ext – [4/18 – 5/2] - extended to 5/9
Thread-Index: AQHVA6Z+hxDeh7jRe0GDjsjKRKT9IQ==
Date: Mon, 06 May 2019 00:56:09 +0000
Message-ID: <SG2PR06MB31765C60D91358999B907F75E1300@SG2PR06MB3176.apcprd06.prod.outlook.com>
References: <00fd01d500ea$e8709fe0$b951dfa0$@ndzh.com>
In-Reply-To: <00fd01d500ea$e8709fe0$b951dfa0$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:EFBE5D8E7DAEABD8C60B0FAB93B5235EE65B45338B3FEF0C7BE91371A4105E96; UpperCasedChecksum:0E7AD75FFB5CA2153F3BA7A7E36FB4CDCA843173482287A9562F4D44BB18570E; SizeAsReceived:6841; Count:42
x-tmn: [bL2wqqp+evsHZb9JD7g8OR1SL7ZEOgrZ]
x-ms-publictraffictype: Email
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(5050001)(7020095)(20181119110)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(9118020)(2017031323274)(2017031324274)(2017031322404)(1601125500)(1603101475)(1701031045); SRVR:SG2APC01HT079;
x-ms-traffictypediagnostic: SG2APC01HT079:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-message-info: 2mTKkVb6gY1rF2ydQl07DqaMBVnfOQ7bOM7BMVAVYgUoBo8WTMwTf5FUFe70Lq2g24rkc2ExrQdU9I1d46XW64YNXWT66YSKRwkuYTRo3Lgssy5VEicGWM+hR/c11nQf5C+xwH71kWU1b7ve0E+efbh2QFskmtePd83yGcXk5J89C/r34Lzd4HL0OndSRZeb
Content-Type: multipart/alternative; boundary="_000_SG2PR06MB31765C60D91358999B907F75E1300SG2PR06MB3176apcp_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: c34eacbf-eef2-416b-dc57-08d6d1bda0b0
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 May 2019 00:56:09.1231 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT079
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/UzNx47QLhnEOjfX1YUa_Y-gbhJ8>
Subject: Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext – [4/18 – 5/2] - extended to 5/9
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 06 May 2019 00:58:08 -0000

support.

Best Regards,
Reta

________________________________
From: Idr <idr-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com>
Sent: Thursday, May 2, 2019 9:28 PM
To: idr@ietf.org
Subject: [Idr] Weekly status 5/2/2019


Greetings idr –



To make sure IDR stays on track until IETF 105, I will be sending out weekly status updates.   Please let me know if these status updates are helpful.



Cheerily, Sue Hares



Status as of 5/2/2019

-------------

Drafts in adoption process:

   The following 3 drafts have no objections and solid reasons behind adoption.

    The chairs will be reviewing these drafts and send out comments on 5/3/2019.



1.       draft-ketant-idr-bgp-ls-app-specific-attrib [4/16-4/30] –

2.       draft-li-idr-bgpls-ls-sbfd-extensions –  [4/18 – 5/2]

3.       draft-ketant-idr-bgp-ls-flex-algo –  [4/16 – 4/30]

4.       draft-wu-idr-bgp-segment-allocation-ext – [4/18 – 5/2]  - extended to 5/9

5.       draft-dawra-idr-bgpls-srv6-ext – [5/2 to 5/16]



The authors of wu-idr-bgp-segment-allocation should start

a discussion to determine all issues have been cleared.



Flow Specification drafts

--------------------------

1)      Flow-specification base draft:  RFC5575bis

   Please review John Scudder’s call for input on the mail list

   regarding the 4 implementation lack of support for:

a)      packet rate in bytes, and

b)      error handling and future NLRI



Flow-specification draft authors should update their documents to include RFC5575bis.

These drafts include:

1.       draft-ietf-idr-bgp-flowspec-oid.txt

2.       draft-ietf-idr-flowspec-l2vpn-09.txt

3.       draft-ietf-idr-flowspec-nvo3-04.txt

4.       draft-ietf-idr-flowspec-path-redirect

5.       draft-ietf-idr-flowspec-interfaceset

6.       draft-ietf-idr-bgp-flowspec-label

7.       draft-ietf-bess-nsh-bgp-control-plane-10



I may have missed another flowpec draft.  If so, would the authors please send me a note.

I would like to start WG LC for flow specification drafts on May 5th.



WG LC

1.       RFC8203bis – [5/6 to 5/20]

Status: Awaiting IPR statement (from John Scudder)



Early allocations calls

------------------------------

no objection noted in the emails, these will be forward to Alvaro and IANA for early allocation:

1.       draft-ietf-idr-nvo3-flowspec-04  -  <https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-nvo3/>

2.       draft-ietf-idr-l2vpn-09.txt   –

3.       draft draft-ietf-idr-te-lsp-distribution



Early allocation call in progress, but some questions in email.

4.       draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]

<https://datatracker.ietf.org/doc/draft-ietf-idr-te-lsp-distribution/>



Chairs/Shepherds

Shepherd write-ups pending (watch for email on 5/3)

1.       draft-ietf-idr-bgp-extended-messages-30 [Sue Hares shepherd]

2.       draft-ietf-idr-bgp-bestpath-selection-criteria [Sue Hares shepherd]



If you have any final comments, please send implementation reports and comments to the shepherd.



The following drafts are undergoing active shepherd engagement

  1.  draft-ietf-idr-tunnel-encaps-11  [John Scudder]
  2.  draft-idr-bgp-optimal-route-reflection [John Scudder]

v2.23.0 | Report a Bug | By Email