Re: [spring] draft-ietf-spring-sr-policy-yang-01

Adrian Farrel <adrian@olddog.co.uk> Sun, 03 December 2023 13:55 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E065C2395EC; Sun, 3 Dec 2023 05:55:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSJyPURtzyjs; Sun, 3 Dec 2023 05:55:15 -0800 (PST)
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 99C48C2395EA; Sun, 3 Dec 2023 05:55:09 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 3B3Dt79h010030; Sun, 3 Dec 2023 13:55:07 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BFDE64604B; Sun, 3 Dec 2023 13:55:07 +0000 (GMT)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A0A1E46048; Sun, 3 Dec 2023 13:55:07 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS; Sun, 3 Dec 2023 13:55:07 +0000 (GMT)
Received: from LAPTOPK7AS653V (82-69-109-75.dsl.in-addr.zen.co.uk [82.69.109.75]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 3B3Dt6sd012176 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 3 Dec 2023 13:55:06 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: bruno.decraene@orange.com, spring@ietf.org
Cc: draft-ietf-spring-sr-policy-yang@ietf.org
References: <CAB75xn5A-1UuqXdoT4VpqsvkzZePKqiYi3ARHtNJ7RtrLZTcfQ@mail.gmail.com> <DM5PR11MB1467B9F28136133477F43632D0869@DM5PR11MB1467.namprd11.prod.outlook.com> <CAB75xn5-O+nCunBdKBhgNzwoGvWMaN3J_hqzq128MKi+_T2Hog@mail.gmail.com> <19878_1664193128_63319268_19878_445_1_2d7414679cdb484b8542e7b9dc5b7bd0@orange.com>
In-Reply-To: <19878_1664193128_63319268_19878_445_1_2d7414679cdb484b8542e7b9dc5b7bd0@orange.com>
Date: Sun, 03 Dec 2023 13:55:05 -0000
Organization: Old Dog Consulting
Message-ID: <03b801da25f0$52a33f60$f7e9be20$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03B9_01DA25F0.52A49EF0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJGSYagSbbWtgGFVvzcJyq5iYZs7AGeTcOpAyZeOcwB3le+aq+KMAjA
Content-Language: en-gb
X-Originating-IP: 82.69.109.75
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=6fjFBjuaj16uT6w8NPLGc YQByJiKIlJ9wJuxvC4xjy8=; b=BIkO7E4E9SeWbPnWV59pkROyx0geqqfrdLLni 5475La206gTaI87E2m01crgQAMCHoSpfSR7c6UVZ12aifZZWWF+FBBxmmhDTakRR rW7LzaPm2ra/FnzDIQLVb6z13xMH0PpZ5ApEFSfpcY84sbyxAF0m5xQxTAoDMrQ4 k71qkLnTcOdztJvInCTkHv+Tq0CSHWjxkOGNdWRa728CxUR9T6I4vx/ghI/isfAi +hY+viQDBjcwv8+sa/l12+T3sioFqTb7SMcZbzYKpcFtLxaDIK2vPppGQsGTjyJ0 Zs3HIfCd3CQxA8YOeKAOUI8JiGcEnVHeu7+3E5K3N7/I7mAwg==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-28036.000
X-TM-AS-Result: No--50.083-10.0-31-10
X-imss-scan-details: No--50.083-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-28036.000
X-TMASE-Result: 10--50.083100-10.000000
X-TMASE-MatchedRID: iKTMlETJ4ps0QDP3j4T8uZnFDQsuYb5/eDbLSPm9dkaXNqgaJF2H4gDl 7jsHDtZzSfS+N55v9tmA8gpLfAL6jriXHQtFEJRKC7Da+oUi6iKOtWfhyZ77DuiOwn7Nhoo1zFa j82CqF9lNHMde8FjyiHeBFpDrNJAWOBdWSuDB7IbTyr0pKxS1VxFbgtHjUWLy9pLnYtQ99xJBqL OmHiM3w7V5+Uf98TSc16yuU//D1D8+ta/415Qhvq88naeSWWBZBcaL/tyWL2PZobCTg4s1LJlhs /AxdKYGkW2ooQJksHcqduy6rUQhOHtUEUnJm6b/vJ+06XVEG4eGFp79YPsyaXDqJXsiEkENdo2c YeC2GcstFsiCldVVEpNS9Qjx4d8fMeoLWiQ8LRSQFNEB5Zw8Rk8PwmaKVerTGWdrIK5nCr8EI2i oyRARN5AIqAV8Qu4jWgBI/3F5doIElEpLb06GvY9GUxQ1nPhLBfZFSDfAcnbzk/ySyYg0Bl7IU0 kLBS2nw0bzZIsWdo61qzGlSaHh7i38M+247Q7B7cVa/IL9hJTvVbHa5Rs8t/2xX1OVrWqLVxt8i PZNr2wqWAJqxcSIYi5E7XYECjTeUnuq6tR+CtX/s+8Vrwj8j1YcxnSBTLTlUaTm5EfQzMJHpEd1 UrzmFf0Rilt9eNz0jQO5NdQooutmQGDcBqEA9dNrjmkAqZmtNmg1ckxsf6cSwak5eNXy+8boqPA 6+88ktZPyUFY5+dAYmbFYWrixJ9kECb6eFouAavaCW5zqiNqL6bUMM+bbIsEiXG0R7qDHDpnuR5 eZKJY/PJ8p+RzsAR72DTGItWXMNJMjNyGsNERJI5ZUl647UBRFJJyf5BJetOt1ofVlaoKm8jxRk 5/juDsrIxPW/QrJCIEb6m1h9zyp/mH7gW9/gAU5rQ/jDZbqhUfR2rvBju6nw52XVXCkJJRMZUCE HkRt
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/gho9Am-TqRylOZuNI08RUEwtzOo>
Subject: Re: [spring] draft-ietf-spring-sr-policy-yang-01
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Dec 2023 13:55:21 -0000

Hey there,

 

So, it's over a year since Bruno asked this question, and eight months since
the current revision expired.

 

I don' see anything on the list, and there was no mention in the meeting at
IETF-118.

 

Can we have a status and plan, please?

It's OK if the authors have decided to give up on their efforts with the
draft, but unless the WG has also given up (it was an adopted draft) it may
be time assign new editors to move forward.

 

Thanks,

Adrian

 

From: spring <spring-bounces@ietf.org> On Behalf Of
bruno.decraene@orange.com
Sent: 26 September 2022 12:52
To: Kamran Raza (skraza) <skraza@cisco.com>;
draft-ietf-spring-sr-policy-yang@ietf.org
Cc: SPRING WG <spring@ietf.org>; Dhruv Dhody <dhruv.ietf@gmail.com>
Subject: Re: [spring] draft-ietf-spring-sr-policy-yang-01

 

Hi Kamran, authors,

 

Thanks for the refreshed draft.

 

What's the status/ETA with regards to incorporating comments from the WG,
e.g. the ones below from Dhruv which are two years/revisions old.

 

Thank you,

Bruno

 

From: spring <spring-bounces@ietf.org <mailto:spring-bounces@ietf.org> > On
Behalf Of Dhruv Dhody
Sent: Wednesday, July 13, 2022 6:00 AM
To: Kamran Raza (skraza) <skraza@cisco.com <mailto:skraza@cisco.com> >
Cc: draft-ietf-spring-sr-policy-yang@ietf.org
<mailto:draft-ietf-spring-sr-policy-yang@ietf.org> ; SPRING WG
<spring@ietf.org <mailto:spring@ietf.org> >
Subject: Re: [spring] draft-ietf-spring-sr-policy-yang-01

 

Hi Kamran, 

 

Thank you! The most important thing to me would be to make the model work at
the device as well as the controller (an example that would be adding
headend into the SR-policy).  

 

Thanks! 

Dhruv

PS. Past comments I sent during adoption -
https://mailarchive.ietf.org/arch/msg/spring/KzXFvavQxwkYLG6unN70JK0Mwno/

 

On Tue, Jul 12, 2022 at 8:29 PM Kamran Raza (skraza) <skraza@cisco.com
<mailto:skraza@cisco.com> > wrote:

Hi Dhruv,

 

The I.D will be refreshed and updated once submissions reopen.

Apologies for the extended delay in updating it .. 

 

Rgds.

 

From: Dhruv Dhody <dhruv.ietf@gmail.com <mailto:dhruv.ietf@gmail.com> >
Date: Tuesday, July 12, 2022 at 10:12 AM
To: draft-ietf-spring-sr-policy-yang@ietf.org
<mailto:draft-ietf-spring-sr-policy-yang@ietf.org>
<draft-ietf-spring-sr-policy-yang@ietf.org
<mailto:draft-ietf-spring-sr-policy-yang@ietf.org> >, SPRING WG
<spring@ietf.org <mailto:spring@ietf.org> >
Subject: draft-ietf-spring-sr-policy-yang-01

Hi Authors/WG, 

 

The I-D in question expired last year! 

 

In fact, there has been no change since its adoption back in May of 2019.
None of the comments received during the adoption calls are handled -
https://mailarchive.ietf.org/arch/msg/spring/9Hy8jfOmVP9vmXXaSJ6mISwYCRM/

 

BTW there are various documents that are importing it -
https://www.yangcatalog.org/yang-search/impact_analysis?rfcs=1
<https://www.yangcatalog.org/yang-search/impact_analysis?rfcs=1&show_subm=1&
show_dir=dependents&modtags=ietf-sr-policy@2019-11-04.yang,ietf-sr-policy-ty
pes@2019-11-04.yang&orgtags=ietf>
&show_subm=1&show_dir=dependents&modtags=ietf-sr-policy@2019-11-04.yang,ietf
-sr-policy-types@2019-11-04.yang&orgtags=ietf

 

Could we get clarity on the status of this I-D? 

 

Thanks! 

Dhruv

 

Orange Restricted

____________________________________________________________________________
_____________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
 
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.