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

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 30 May 2019 13:52 UTC

Return-Path: <adrian@olddog.co.uk>
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 59659120164 for <idr@ietfa.amsl.com>; Thu, 30 May 2019 06:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 K_0A5nYcAxCq for <idr@ietfa.amsl.com>; Thu, 30 May 2019 06:51:58 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 241431200C1 for <idr@ietf.org>; Thu, 30 May 2019 06:51:57 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x4UDpt0Y025449; Thu, 30 May 2019 14:51:55 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DA11922044; Thu, 30 May 2019 14:51:54 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs3.iomartmail.com (Postfix) with ESMTPS id CE46B2203C; Thu, 30 May 2019 14:51:54 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.172.175]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x4UDprdV020570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 30 May 2019 14:51:53 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Susan Hares'" <shares@ndzh.com>, <idr@ietf.org>
References: <00fd01d500ea$e8709fe0$b951dfa0$@ndzh.com>
In-Reply-To: <00fd01d500ea$e8709fe0$b951dfa0$@ndzh.com>
Date: Thu, 30 May 2019 14:51:52 +0100
Organization: Old Dog Consulting
Message-ID: <039101d516ee$d6b1c620$84155260$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0392_01D516F7.38762E20"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQI3cxoAp+Zyr7LrJqeQ1oTG1h1goqW+9Kqw
Content-Language: en-gb
X-Originating-IP: 87.112.172.175
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24646.007
X-TM-AS-Result: No--21.996-10.0-31-10
X-imss-scan-details: No--21.996-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24646.007
X-TMASE-Result: 10--21.995900-10.000000
X-TMASE-MatchedRID: CxmI61mtwh9D9/Mxo/zsk3FPUrVDm6jtUb4EdIZGxuAG2HMvWEJenp+3 MmAXSezSL05nWg7if/ADGrOBgK/eYf63A8K+i2hWNqGNk8Sh2Rd1zSnwpu89bXy/Hx1AgJrrocM xOHJmdvOAT8geMwPsRN2zZGcigPKlz0fUQO65Z+cJteOxcC2tilsP0tBwe3qDI0FYZlCQVHzx4t +6y2InAhi0kqb6DUBiN+sVwGjgynMIVdJlj1AInpVRzPxemJL0FcdDdkw5aTY4WCCtJolgRexvA Z+P6819TSKi/hLbJnw8CyC5jWhXvEzOmjZzSvazsp7Uow62+uGUUZS7sMHOGG0emrRhsFGLg7df cgkv9hnfygTLjAbg7Bhay2YaNP/D4ldmRpDaVOHTHyifga1nxzsY2/UEG7fkg8vHe9ji82I0VlF e0MnlXqiqmC7TOCvq9JV2OQc0/oMon/tyXrDS/fNmGUwdG/ivojQrbrPpzzrieGQLRIaTJHJ2g7 BJb0I1iRsciu850EfLEb2T0e7D/8aYrv2w73pJUFJbPlmBv8NnLk6tQLcY6b30nMkbSmkdv9s2A vZF5QrduspQUf2VXf6FWf3G2+PkNQ5dIDsl0O/aO/4pZ7P7diiDcgXvAzWyv27awoUD83Qpxi26 x4kFRV+KIlikOuMDAH/xyJs7whhHW+94FA8JF8K1Ib9JAALxrogFtKd/P7cLBZEuqIL9SpO9mQG x4jC3Sa7i4WMGYwF/2SsgU8jyNW7vEKjEI8LygNylVbI/EAyoCf7IdvPAJzAx/HIgP92dNEZZmA O2JUgV2zUx68mUz1l5gHXJcVkKhKGmKhzU0vKeAiCmPx4NwGmRqNBHmBvevqq8s2MNhPDPPeN6H N6d7M+9+OQ9U/5f33fj+sMArfOEbaqKQSlAZfA+CYwMWBiiNOPx9da4Uw2OCP9cFz4ygkQurNK6 R3r9DuPosnMBddo=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/o1PgG3v8eIILl9B1TrPe07mlZiI>
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, 30 May 2019 13:52:01 -0000

Hi Sue,

 

Wrt your item 1)b)7 on draft-ietf-bess-nsh-bgp-control-plane-10.

 

The authors have been discussing this and have agreed:

 

OLD

   [RFC5575] defines a set of BGP routes that can be used to identify

   the packets in a given flow using fields in the header of each

   packet, and a set of actions, encoded as extended communities, that

   can be used to disposition those packets.  This document enables the

   use of RFC 5575 mechanisms by SFC Classifiers by defining a new

   action extended community called "Flow Spec for SFC classifiers"

   identified by the value TBD4.  Note that other action extended

   communities may also be present.

NEW

    [RFC5575]  and [I-D.ietf-idr-rfc5575bis] define a set of BGP routes

    that can be used to identify the packets in a given flow using fields

    in the header of each packet, and a set of actions, encoded as

    extended communities, that can be used to disposition those

    packets.  This document enables the use of these mechanisms by

    SFC Classifiers by defining a new action extended community called

    "Flow Spec for SFC Classifiers" identified by the value TBD4.  Note

    that other action extended communities MUST NOT be present at

    the same time: the inclusion of the "Flow Spec for SFC Classifiers"

    action extended community along with any other action MUST be 

    treated as an error which SHOULD result in the Flow Specification

    UPDATE message being handled as Treat-as-withdraw according to

    [RFC7606] Section 2.

END

 

Best,

Adrian

 

From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares
Sent: 02 May 2019 14:28
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  -  
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]