IETF Logo Mail Archive

[Tools-discuss] Fwd: New Internet-Draft waiting for approval: draft-ssangli-idr-bgp-generic-metric

Jeffrey Haas <jhaas@pfrc.org> Mon, 08 July 2024 14:00 UTC

Return-Path: <jhaas@pfrc.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCC44C14CF13; Mon, 8 Jul 2024 07:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 2phMoNuwaZIM; Mon, 8 Jul 2024 07:00:11 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id D2E18C1CAE8F; Mon, 8 Jul 2024 07:00:10 -0700 (PDT)
Received: from smtpclient.apple (172-125-100-52.lightspeed.livnmi.sbcglobal.net [172.125.100.52]) by slice.pfrc.org (Postfix) with ESMTPSA id 1753C1E039; Mon, 8 Jul 2024 10:00:10 -0400 (EDT)
From: Jeffrey Haas <jhaas@pfrc.org>
Message-Id: <4F84892C-21A3-46CC-986D-FDDC4E59A85C@pfrc.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_524BF174-1F69-4890-86E9-150F8B3F1320"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.8\))
Date: Mon, 08 Jul 2024 10:00:09 -0400
References: <172018680047.1354870.10412530143856717047@dt-datatracker-5f88556585-g8gwj>
To: tools-discuss@ietf.org
X-Mailer: Apple Mail (2.3696.120.41.1.8)
Message-ID-Hash: I7MRORG7TAK6K4AERI2DHX5O3IIZUU2E
X-Message-ID-Hash: I7MRORG7TAK6K4AERI2DHX5O3IIZUU2E
X-MailFrom: jhaas@pfrc.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: idr chairs <idr-chairs@ietf.org>, Srihari Sangli <ssangli@juniper.net>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Fwd: New Internet-Draft waiting for approval: draft-ssangli-idr-bgp-generic-metric
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/-Jh2ieYR5wkA9yazaXYxnyzlQBQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

It may simply be too early in my morning to see what's going on here, but why has this draft been flagged for chairs' approval?  The draft is in the form of draft-NAME-WG where IDR is an active WG.

-- Jeff


> Begin forwarded message:
> 
> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Subject: New Internet-Draft waiting for approval: draft-ssangli-idr-bgp-generic-metric
> Date: July 5, 2024 at 9:40:00 AM EDT
> To: <idr-chairs@ietf.org>
> Resent-From: <alias-bounces@ietf.org>
> Resent-To: jhaas@pfrc.org, jie.dong@huawei.com, keyur@arrcus.com, skh@ndzh.com
> 
> 
> Hi,
> 
> Chair approval is needed for posting of draft-ssangli-idr-bgp-generic-metric-00.
> 
> Note: This submission belongs to an inactive working group.
> 
> To approve the Internet-Draft, go to this URL (note: you need to login to be able to approve):
>  https://datatracker.ietf.org/submit/status/143818/5a2131db17aea75fff3c06ac4cbebed1/
> 
>  File name       : draft-ssangli-idr-bgp-generic-metric
>  Revision        : 00
>  Submission date : 2024-07-05
>  Group           : Individual Submission
> 
>  Title           : Accumulated Metric in NHC attribute
>  Document date   : 2024-07-05
>  Pages           : 22
>  File size       : 51.7 KB
> 
>  Submitter       : Srihari Sangli <ssangli@juniper.net>
> 
>  Abstract        :    RFC7311 describes mechanism for carrying accumulated IGP cost across
>   BGP domains however it limits to IGP-metric only.  There is a need to
>   accumulate and propagate different types of metrics as it will aid in
>   intent-based end-to-end path across BGP domains.  This document
>   defines BGP extensions for Generic Metric sub-types that enable
>   different types of metrics to be accumulated and carried in BGP.
>   This is applicable when multiple domains exchange BGP routing
>   information.
> 
> 
> 
>  Authors:
>    Srihari Sangli <ssangli@juniper.net>
>    Shraddha Hegde <shraddha@juniper.net>
>    Reshma Das <dreshma@juniper.net>
>    Bruno Decraene <bruno.decraene@orange.com>
>    Bin Wen <bin_wen@comcast.com>
>    Marcin Kozak <marcin_kozak@comcast.com>
>    Jie Dong <jie_dong@huawei.com>
>    Luay Jalil <luay.jalil@verizon.com>
>    Ketan Talaulikar <ketant.ietf@gmail.com>
> 
> 
> 
> 
> Best regards,
> 
> 	The IETF Secretariat
> 	through the Internet-Draft submission service

v2.41.0 | Report a Bug | By Email | System Status