Re: [Idr] IDR Charter discussion

"UTTARO, JAMES" <ju1738@att.com> Thu, 25 July 2019 11:01 UTC

Return-Path: <ju1738@att.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 6455F120134 for <idr@ietfa.amsl.com>; Thu, 25 Jul 2019 04:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-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 y3e5vmf2Veiz for <idr@ietfa.amsl.com>; Thu, 25 Jul 2019 04:01:35 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 1209812010C for <idr@ietf.org>; Thu, 25 Jul 2019 04:01:35 -0700 (PDT)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x6PAsr3q008287; Thu, 25 Jul 2019 07:01:33 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049459.ppops.net-00191d01. with ESMTP id 2ty9hr9weu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 25 Jul 2019 07:01:33 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x6PB1XUH027446; Thu, 25 Jul 2019 07:01:33 -0400
Received: from zlp27130.vci.att.com (zlp27130.vci.att.com [135.66.87.38]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x6PB1QFO027362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 25 Jul 2019 07:01:27 -0400
Received: from zlp27130.vci.att.com (zlp27130.vci.att.com [127.0.0.1]) by zlp27130.vci.att.com (Service) with ESMTP id B35104009E91; Thu, 25 Jul 2019 11:01:26 +0000 (GMT)
Received: from MISOUT7MSGHUBAH.ITServices.sbc.com (unknown [130.9.129.152]) by zlp27130.vci.att.com (Service) with ESMTPS id 9BC914005C3C; Thu, 25 Jul 2019 11:01:26 +0000 (GMT)
Received: from MISOUT7MSGUSRCD.ITServices.sbc.com ([169.254.4.104]) by MISOUT7MSGHUBAH.ITServices.sbc.com ([130.9.129.152]) with mapi id 14.03.0439.000; Thu, 25 Jul 2019 07:01:26 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, Susan Hares <shares@ndzh.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] IDR Charter discussion
Thread-Index: AQHVQY30JjTNR9UET6u0Mkxr6DnpI6baaHwAgADE3OA=
Date: Thu, 25 Jul 2019 11:01:25 +0000
Message-ID: <B17A6910EEDD1F45980687268941550F4D891015@MISOUT7MSGUSRCD.ITServices.sbc.com>
References: <022b01d51fc5$d6576dd0$83064970$@ndzh.com> <20190723193643.GB81521@vurt.meerval.net> <31830_1563995779_5D38AE83_31830_59_1_53C29892C857584299CBF5D05346208A48BB75A8@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
In-Reply-To: <31830_1563995779_5D38AE83_31830_59_1_53C29892C857584299CBF5D05346208A48BB75A8@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.70.224]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-25_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1907250131
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TgEqa-ZdePK-X7saGpNU4kTu628>
Subject: Re: [Idr] IDR Charter discussion
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, 25 Jul 2019 11:01:38 -0000

+1.

Thanks,
	Jim Uttaro

-----Original Message-----
From: Idr <idr-bounces@ietf.org> On Behalf Of bruno.decraene@orange.com
Sent: Wednesday, July 24, 2019 3:16 PM
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org
Subject: Re: [Idr] IDR Charter discussion

Dear Susan,

May be adding "BGP persistence",
(possibly depending on whether we believe the charter will be updated before or after we send this draft to IESG)
possibly under the umbrella "Improving BGP resiliency" which IMHO may be a general subject which should be of interest.

Kind regards,
--Bruno

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Job Snijders
Sent: Tuesday, July 23, 2019 3:37 PM
To: Susan Hares
Cc: idr@ietf.org
Subject: Re: [Idr] IDR Charter discussion

Dear Susan,

Perhaps "clean-up of some old things" can be added to the charter. 

As an example, I think a draft like this should go through the WG
towards publication: https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dkumari-2Ddeprecate-2Das-2Dset-2Dconfed-2Dset&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=AYAzJIWAdfG6oJV_HANFmeQx9Us3rQHhwPYg-qhD3Gk&s=wxwU9vgPykqi78ct7aDclyjClHviwN60zGkgICp4wdQ&e=

Kind regards,

Job

On Mon, Jun 10, 2019 at 03:51:03PM -0400, Susan Hares wrote:
> The IDR Charter was last revised in March, 2010. 
> 
>  
> 
> It's time to reconsider what needs to go in the charter: 
> 
>  
> 
> Somethings we might include are:
> 
> ..         BGP Yang modules, 
> 
> ..         A general BGP Layer 3 auto-configuration or liveness, 
> 
> ..         Additional  tunnel features for a optional tunnel encapsulation (a
> follow-on to draft-ietf-idr-tunnel-encaps), 
> 
> ..         Upgrade of the base BGP specification to Full Standard, 
> 
> ..         Flow specification additions, 
> 
> ..         BGP-LS basic functions (e.g.
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dketant-2Didr-2Drfc7752bis_&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=AYAzJIWAdfG6oJV_HANFmeQx9Us3rQHhwPYg-qhD3Gk&s=xsdmD6TNZklFu28809bEFYvbt3bZRC6QwW8eyvqQxT0&e=>
> draft-ketant-idr-rfc7752bis-00) error handling
> 
> ..         Segment routing additions to BGP, 
> 
> ..         Wide Communities and other "bigger" communities , 
> 
> ..         Revisions to Existing features. 
> 
>  
> 
>  
> 
> Things which will be removed because we are done: 
> 
> ..         Support for 4-octet AS numbers, 
> 
> ..         Add path related additions, 
> 
> ..         Error handling rules for BGP in general, 
> 
> ..         Revisions to the BGP 'Minimum Route Advertisement Interval', 
> 
> ..         The definition of an "Accumulated IGP Metric".
> 
>  
> 
> In 2010, IDR started an advancement of BGP to full standard, but stopped. 
> 
> WG members indicated they wanted us to focus on the feature revisions. 
> 
>  
> 
> Is there anything we missed? 
> 
>  
> 
> Please use this thread to suggest things we should keep or drop in the
> charter. 
> 
>  
> 
> Cheerily, Susan Hares
> 

> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_idr&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=AYAzJIWAdfG6oJV_HANFmeQx9Us3rQHhwPYg-qhD3Gk&s=Jf_H1hSTcqGjf15nRiqNQt11ibvDliWiRymQ3jPRE8Q&e=

_______________________________________________
Idr mailing list
Idr@ietf.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_idr&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=AYAzJIWAdfG6oJV_HANFmeQx9Us3rQHhwPYg-qhD3Gk&s=Jf_H1hSTcqGjf15nRiqNQt11ibvDliWiRymQ3jPRE8Q&e=

_________________________________________________________________________________________________________________________

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.

_______________________________________________
Idr mailing list
Idr@ietf.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_idr&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=AYAzJIWAdfG6oJV_HANFmeQx9Us3rQHhwPYg-qhD3Gk&s=Jf_H1hSTcqGjf15nRiqNQt11ibvDliWiRymQ3jPRE8Q&e=