Re: [Idr] Weekly status 5/2/2019

"Acee Lindem (acee)" <acee@cisco.com> Thu, 02 May 2019 18:22 UTC

Return-Path: <acee@cisco.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 96276120125 for <idr@ietfa.amsl.com>; Thu, 2 May 2019 11:22:01 -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=F61G2xrL; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ZeNK03g5
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 e4G5nv85f1CG for <idr@ietfa.amsl.com>; Thu, 2 May 2019 11:21:59 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5824A120075 for <idr@ietf.org>; Thu, 2 May 2019 11:21:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=41603; q=dns/txt; s=iport; t=1556821319; x=1558030919; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=fXJhDeYdCWvyWPnTwJRmwbWqfqCy7JB9dq64omZ7ip8=; b=F61G2xrLrcaq1ECCmnWsDbBsOCi2PHjbjY4fqoTnClqAL333nDlB5+dq hFfwrDvqjf4eNNewxh2NkqwTgCoAV3x979MdvSlCkdSmXSdoWdtZ7bj8h nXw+2S1XEK0ilbKnzKOn3AUhM8nJUF41FEAULiRuNtUn8sNQRjBJEBHi/ c=;
IronPort-PHdr: =?us-ascii?q?9a23=3AVWkfzhKLqKaBE4SwV9mcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeCuKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuMAkD2BPXrdCc9Ws9FUQwt8g=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AJAADqM8tc/49dJa1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUQUBAQEBCwGBDi9QA2lVIAQLKAqEBoNHA4RSijFKgWglfpY?= =?us-ascii?q?kgS4UgRADVA4BAS2EQAIXhhwjNAkOAQMBAQQBAQIBAm0cDIVKAQEBBBILBgo?= =?us-ascii?q?TAQE4DwIBCA4DAwECIQEJAgICMB0IAQEEARIigwABgR1NAx0BAqMzAoE1iF9?= =?us-ascii?q?xgS+CeQEBBYJHgjwYgXQaCYEyAYtLF4F/gREnDBOCFzU+gQSDDQERAgE+gmo?= =?us-ascii?q?ygiaKeBuCOoRLlRAJAoIJkkAbgg6GPIs1gUKMFoEgOJMLAgQCBAUCDgEBBYF?= =?us-ascii?q?POGVxcBU7KgGCQYIPCQMMC4NMilNygSmSEwGBIAEB?=
X-IronPort-AV: E=Sophos;i="5.60,422,1549929600"; d="scan'208,217";a="266596822"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 May 2019 18:21:58 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x42ILwrl011335 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 2 May 2019 18:21:58 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 2 May 2019 13:21:57 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 2 May 2019 13:21:56 -0500
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 2 May 2019 13:21:56 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fXJhDeYdCWvyWPnTwJRmwbWqfqCy7JB9dq64omZ7ip8=; b=ZeNK03g5CRKPaio8a8DWGpA8dnSVZRpN6UFX3W5mJpjO3YZhutnPiRGFduWCRPGkcKfaTuY9JxCcNdkJhJ5VEKnyR3C9aQ9HbLwmRcZnQ+dOaFS5raqCBWo7O//IOAeXvPhBjElGJ8fAlXzo1/IHDG8/4T1JaAZlivc9OeQdw9s=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB3437.namprd11.prod.outlook.com (52.135.127.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1835.15; Thu, 2 May 2019 18:21:55 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::5c42:5f15:d194:98f]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::5c42:5f15:d194:98f%5]) with mapi id 15.20.1835.018; Thu, 2 May 2019 18:21:55 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Weekly status 5/2/2019
Thread-Index: AdUA5TbE8WM5MwuRRe2vYSq7mwOEQQADS1oA
Date: Thu, 2 May 2019 18:21:55 +0000
Message-ID: <AF27EED9-9292-4873-9463-C627809C83C9@cisco.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:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [173.38.117.82]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6939c8d3-12ec-4c1c-0ae4-08d6cf2b0e8f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:SN6PR11MB3437;
x-ms-traffictypediagnostic: SN6PR11MB3437:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <SN6PR11MB343789BDD850505FEFA1FDB7C2340@SN6PR11MB3437.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0025434D2D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(346002)(39860400002)(136003)(396003)(376002)(189003)(199004)(9763003)(6246003)(86362001)(476003)(478600001)(76176011)(446003)(26005)(486006)(5660300002)(229853002)(53936002)(11346002)(316002)(68736007)(14454004)(110136005)(8936002)(36756003)(6486002)(2616005)(66556008)(73956011)(25786009)(6116002)(54896002)(14444005)(83716004)(66066001)(71190400001)(6506007)(2501003)(71200400001)(6436002)(99286004)(66446008)(33656002)(66476007)(8676002)(256004)(64756008)(66946007)(2906002)(91956017)(102836004)(6512007)(3846002)(7736002)(81166006)(82746002)(81156014)(76116006)(53546011)(6306002)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3437; H:SN6PR11MB2845.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: eTIGK6VEsWueNwT2mEKqWJr6By2UE8hTuVmM7AE4F0E++yVLHAuHTMn3//m4NbDV4TMVdA5YOQdb67qF45EygkQAC/U20Rbg84cTupiOQSLZ9SmRrhOqzGRRhao8Ag5xRYFOw05QbSdgskonX1oNaJ7k8Ry8pE6fmOOcTR3BIQ/epHMugPZ6bqqnMtnH0c8F0t8hU0qe+23aRFq3+b8oxiVT0RO1Tb0o5KOi4ROn4feTXBxezPdbSqGpV1noU52//2MDTlGu9WP3N1ycS+dKWnm3q4YWv69ZWAoC9ovYg+isPRgPZxYJwesQEpEqf6GJeRxT33guOm9zuEncVpCiR6krbjyWnY0OqU4hse2sZvWtngO+Upjn5HD47AHIy2AyYoKPmseNBUtgFQU/NziZ0RrcVaVakc6p4yjzx7TQlKg=
Content-Type: multipart/alternative; boundary="_000_AF27EED9929248739463C627809C83C9ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6939c8d3-12ec-4c1c-0ae4-08d6cf2b0e8f
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 May 2019 18:21:55.2641 (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-Transport-CrossTenantHeadersStamped: SN6PR11MB3437
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qv3tNzgyfYy6ik70RW7tcYm_Z9c>
Subject: Re: [Idr] Weekly status 5/2/2019
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: Thu, 02 May 2019 18:22:02 -0000

It would be extremely useful to highlight any changes from week to week (or only include changes in the status).
Acee

From: Idr <idr-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com>
Date: Thursday, May 2, 2019 at 9:28 AM
To: IDR List <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  -

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]

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]