Re: [Idr] IDR WG Charter (Re: Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018])

John Scudder <jgs@juniper.net> Fri, 07 June 2019 15:27 UTC

Return-Path: <jgs@juniper.net>
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 B98781200DE; Fri, 7 Jun 2019 08:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level:
X-Spam-Status: No, score=-2.709 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 ynOIYrr1fRHD; Fri, 7 Jun 2019 08:27:09 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 723AA120026; Fri, 7 Jun 2019 08:27:09 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x57FJREI027631; Fri, 7 Jun 2019 08:27:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=ECEk8rjFtt2VeFaXZVUsl4UItc4WCaRuKAiEu96w4io=; b=YGqRnwnvQ+Dc++KbkHtP0lf+4YdMi1x+XWGIX0T4LeSG5zj+etIqY2oY8s/26Yo3Rwn4 Xx5IPEU+txcnNzSCdhpgG20JQKrj+TQL+LsedTt11Gz9kK/xjoDE/fRkWclhTBp/ZPd9 sgWB8NO8fbGnAvDj4P/MIG6LHjEFZqspjhQOLFdEX7ITHtkGz/aUhF268ZOZnUprz4Kv HaxHWFggtYfCD1EVNOEFsPBK43Z3ZJP/RrZDgLY1Fml4UUqWYfZSXFTKYKMYtCbaUINb vqjsMb+JK2eCab+Bt1DBm1viXvoNYwM4N+6cFW1xAmmDuOTqcAAjnM17G5H9XCmeYnXm 7Q==
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp2056.outbound.protection.outlook.com [104.47.40.56]) by mx0a-00273201.pphosted.com with ESMTP id 2sykgcgmwu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 07 Jun 2019 08:27:06 -0700
Received: from DM6PR05MB4714.namprd05.prod.outlook.com (20.176.109.215) by DM6PR05MB6092.namprd05.prod.outlook.com (20.178.30.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.12; Fri, 7 Jun 2019 15:27:04 +0000
Received: from DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::1549:ffd0:8373:4593]) by DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::1549:ffd0:8373:4593%3]) with mapi id 15.20.1987.004; Fri, 7 Jun 2019 15:27:04 +0000
From: John Scudder <jgs@juniper.net>
To: Alvaro Retana <aretana.ietf@gmail.com>
CC: Robert Raszuk <robert@raszuk.net>, "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>, "idr@ietf. org" <idr@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>, Hares Susan <shares@ndzh.com>
Thread-Topic: [Idr] IDR WG Charter (Re: Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018])
Thread-Index: AQHVG5xWF/Wjx7EUZE6YwT/lqcwvA6aQU7GA
Date: Fri, 7 Jun 2019 15:27:04 +0000
Message-ID: <08F80367-B5B7-408F-94CA-E76D652B144C@juniper.net>
References: <01ce01d5167f$d263a120$772ae360$@ndzh.com> <DM5PR11MB202720F61953C224DB081498C1140@DM5PR11MB2027.namprd11.prod.outlook.com> <02cf01d51ab1$052bfc80$4001a8c0@gateway.2wire.net> <004201d51abd$498a5000$dc9ef000$@ndzh.com> <CAOj+MMEnyT1sOX9fWbDR4PV4goBZerdF6ykKUbZ2t3YDRyAHfg@mail.gmail.com> <005301d51ac3$4b6e6a90$e24b3fb0$@ndzh.com> <CAOj+MMHV0G_O9p7F0UPHXUtzz6HWSiVa5EsLosZu3Q7U_Gr32A@mail.gmail.com> <CAMMESsyKX3KwbgFVb6v2jzWixn6nJLrBZezdQMpxNH4ExvzTYQ@mail.gmail.com>
In-Reply-To: <CAMMESsyKX3KwbgFVb6v2jzWixn6nJLrBZezdQMpxNH4ExvzTYQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [162.225.191.79]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9377bca0-1276-4e69-3c4b-08d6eb5c9821
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:DM6PR05MB6092;
x-ms-traffictypediagnostic: DM6PR05MB6092:
x-microsoft-antispam-prvs: <DM6PR05MB609209B5F888478331A59D69AA100@DM6PR05MB6092.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0061C35778
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(136003)(376002)(366004)(346002)(189003)(199004)(476003)(229853002)(14454004)(11346002)(26005)(2616005)(446003)(66066001)(68736007)(186003)(53936002)(6436002)(6486002)(33656002)(6246003)(82746002)(66446008)(6506007)(53546011)(64756008)(76176011)(99286004)(66476007)(66556008)(76116006)(73956011)(66946007)(4744005)(102836004)(54906003)(316002)(81156014)(81166006)(6116002)(256004)(4326008)(8676002)(5660300002)(6916009)(86362001)(25786009)(3846002)(83716004)(71200400001)(71190400001)(8936002)(486006)(7736002)(36756003)(2906002)(236005)(6512007)(478600001)(54896002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB6092; H:DM6PR05MB4714.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: nd5ozXZzLkkvrlcYZBywKbJ0llxoECpYrF2fAplaxjcf9Dmhi9ncFbudbnb0a8k8VnHUbczH5b8/6X+6gajAMid8dLLdUIONLnXdUQMHUsKyGPdj9ORLAwOjv12//LNrHlm8SQSo75KVdbumTYu+K0AcpQMk4rWFE8PwWxHrjumPaP/7mof+pZEJyZ7Pb5wsE0VYplE5nCr9qf3Rff+GZW54UDb8dB3wdw5AHloDrOZv3B/UK76mA+1pihuRwucRHmuohtNGWqIJp+XjLoMxzNleur2gKCljI4EOV7bSaFr+UOATsf0GzhgxaLVRnyGOWCuItZC3R0OJKvbDb4nzzB4oI2jNJHM5kxhItKVheN7FtvoInY+rnTH5Tp/rQR0h3jlQjoiZYlhpUpV6TAWGQXye/9Lgh3ydQhgZIezTuUY=
Content-Type: multipart/alternative; boundary="_000_08F80367B5B7408F94CAE76D652B144Cjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 9377bca0-1276-4e69-3c4b-08d6eb5c9821
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jun 2019 15:27:04.0637 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jgs@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB6092
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-07_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=697 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906070107
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LgBUyq-iQVJb7e0HxSnNrUP6TdY>
Subject: Re: [Idr] IDR WG Charter (Re: Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018])
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: Fri, 07 Jun 2019 15:27:11 -0000

On Jun 5, 2019, at 8:43 AM, Alvaro Retana <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>> wrote:

I have also had the conversation with the Chairs about the load that BGP-LS represents to idr and the general topic of information transport (note that BGP is not the only protocol in the Routing Area being used to transport stuff…so it is a much wider topic).  The last time was a few months ago.  I don’t remember having the discussion on the list.

At that time, the general consensus (between the Chairs and me) was that the operation of BGP-LS should be maintained in idr (it is BGP!).

One further outcome of that discussion was that we agreed that LSR would include a BGP-LS encoding when progressing uncomplicated drafts that already contain OSPF and IS-IS encodings. We reported this to the WG at our meeting and it’s come up on the mailing list since then. My hope is this will reduce overhead for all concerned.

—John