Re: [Idr] Adoption call for draft-ketant-idr-rfc7752bis-01.txt [8/8 to 8/22]

Balaji Rajagopalan <balajir@juniper.net> Mon, 19 August 2019 17:02 UTC

Return-Path: <balajir@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 3596F120089 for <idr@ietfa.amsl.com>; Mon, 19 Aug 2019 10:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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] 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 U4_lEth8GC49 for <idr@ietfa.amsl.com>; Mon, 19 Aug 2019 10:02:12 -0700 (PDT)
Received: from mx0b-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 82EFA12004C for <idr@ietf.org>; Mon, 19 Aug 2019 10:02:12 -0700 (PDT)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x7JH06Wd021823; Mon, 19 Aug 2019 10:02:11 -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=ak8ar/fAYo0tP9sedZpED9vQRr4GDwVSNClym8dAKQU=; b=mSIcEmdZ5vtzFur3wnl5C/SyJ/cUjRs2q8YU/NQIAzzVnrlWDIAZ5amOB9uCrwvEoqdx jqtvF1jicbPYPnmVwVEqpvtW+Fu/lzhvaVPSX82axMr89sACdekNE17wlcO9j92ILcFB 6teEg3BvmKAN0pevPfbZB6QhuEtr/nsq8xzn3i25W8bhWBVAWsNsrLoTInp/kh5UHPi2 +onkbveIjenCVNdhf5/xRFbR7H6M75yET38Lxt4bmsc/9F2pq1sJ0uo39WnSd22k+BMe 19cOhKTFabfuXitPhLN6/f3GbeD05nIOKBG07v82jzRuUl5ldKUb7WlEdWrJpd65w/D9 FA==
Received: from nam05-by2-obe.outbound.protection.outlook.com (mail-by2nam05lp2054.outbound.protection.outlook.com [104.47.50.54]) by mx0a-00273201.pphosted.com with ESMTP id 2ufw4gr9d7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 19 Aug 2019 10:02:06 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=A/pUHkh4SWyrJ6fcSuNbZ8MQXVAVoPYMVmUn/YdTu0Yu/tRdfcAdWwvlcJ2Zys36QhhUbYIFpfo2514lYz3lqwQpfjlkZgXc+Mll2QFsL3yw4IO3JDzQcqGpbAordu0RQFDdxJgA/6PMf+mAsGC726AhnbgGB+gZa4y8g9hjfIv4jhPqjaykenWObNHlKC5jAehtnCZ8Tt6kgAQeHiu9UNi/CvjjmSs1YzGgCXUC5kcyFOsgIrKUnUn/Dagc08y+BZK3/KOLlfVipYfXFklunnxmsECLfPoFnIaCM+e6F78KTO9ffdmJ7m+cYfHiGstLlCo7p+RKCNVHemol2iIb6g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ak8ar/fAYo0tP9sedZpED9vQRr4GDwVSNClym8dAKQU=; b=CnB+5k0iogD/SvfIXknPkyHFb/6Lyz2du+/M5bfm4sxl1Io3Y0G+3D88nrg1J2UtmgaANdiVZY6OP56PmA5sGKxyYZVIofqJa+MoEq/RSNn2ylL+wQNA9x3lDaK0LMPjNChqqszK7+w4QEJUf0A3u9zYTTxMXBiDSRBcdIhqu8GX0NDS0sC5GBKIO+6Xi5ONxLcYeopy1CYeI1kh3t4Dx8KHWUMvQ2RD1caNqx+73D+jPAEqo/Ao6dgK2n2OjfISq9h4CkD2wxVPLDiSS9gcFhfm4ClYas6oHPLKd2eBY5P+PkA5T+7aDIxK253vcOU57mPYeRzBpcJB4uLvXyV8RA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
Received: from MN2PR05MB6189.namprd05.prod.outlook.com (20.178.243.224) by MN2PR05MB6448.namprd05.prod.outlook.com (20.178.247.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.14; Mon, 19 Aug 2019 17:02:02 +0000
Received: from MN2PR05MB6189.namprd05.prod.outlook.com ([fe80::69d5:25ef:fbab:c12d]) by MN2PR05MB6189.namprd05.prod.outlook.com ([fe80::69d5:25ef:fbab:c12d%7]) with mapi id 15.20.2199.011; Mon, 19 Aug 2019 17:02:02 +0000
From: Balaji Rajagopalan <balajir@juniper.net>
To: 'Susan Hares' <shares@ndzh.com>
CC: 'idr wg' <idr@ietf.org>
Thread-Topic: [Idr] Adoption call for draft-ketant-idr-rfc7752bis-01.txt [8/8 to 8/22]
Thread-Index: AdVOH5HoHfsN7/tjRt2OgDiNu7rv6QGD8qiAAKujpoA=
Date: Mon, 19 Aug 2019 17:02:02 +0000
Message-ID: <884B3A45-93AF-4CC2-86DA-3347F32268C4@juniper.net>
References: <000c01d54e1f$db81b080$92851180$@ndzh.com> <028001d5542f$5fe5cef0$1fb16cd0$@olddog.co.uk>
In-Reply-To: <028001d5542f$5fe5cef0$1fb16cd0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1c.0.190812
x-originating-ip: [116.197.184.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8d981912-a7af-42a5-f1b3-08d724c6f4c7
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR05MB6448;
x-ms-traffictypediagnostic: MN2PR05MB6448:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR05MB64487CB6D5F1239413CCA14DABA80@MN2PR05MB6448.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0134AD334F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(366004)(346002)(396003)(376002)(136003)(39860400002)(199004)(189003)(6246003)(36756003)(64756008)(14454004)(2906002)(99286004)(8936002)(316002)(446003)(14444005)(86362001)(6486002)(6916009)(229853002)(6506007)(6512007)(54896002)(6116002)(66446008)(11346002)(486006)(2616005)(6436002)(33656002)(478600001)(7736002)(81166006)(8676002)(76176011)(58126008)(66556008)(3846002)(66066001)(102836004)(6306002)(53546011)(186003)(71200400001)(76116006)(81156014)(71190400001)(53936002)(476003)(25786009)(4326008)(26005)(5660300002)(66946007)(256004)(66476007)(91956017)(574754004); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR05MB6448; H:MN2PR05MB6189.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: rdVNEuvTVTxcDlMyShGnbOdQX+icPQx6FPkGw2VbyvoLhYVsDsJttlv1doBocNYkKO3KyH0I9+sNHSZJ6gUokZNndW0hIoV17MIfqpWmhUFttVDHA10Tqe2SA8nkNKUbCmRjaNstaQmZA0M+zrN+plKMtD4v/Y15qLIAZSx6pVjyDK3oVMfqJ8ScKxATqKzN/QendC7jmYqZ3L4kJyK76EPsgmR08sCoWqa87UMLzALxZCGpZYVA9E8qSHwnmKOqpI+utKU5VTlrE+jtqqw49KRgtTZO7J7hGM2CVtECfWt0KqM+r4jjQVR/I9C5rxg00qEw9r5NO06WuYOz/ihY2PmCZxO2G9V4GJSp4Ou/T7DOL/W8haXK4yMuWP2eBf878hEqmcfp16TubQEEeitvH/bV3qIQib/5/4xlM3R/tC0=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_884B3A4593AF4CC286DA3347F32268C4junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 8d981912-a7af-42a5-f1b3-08d724c6f4c7
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2019 17:02:02.2714 (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: 0hn/Aythr27Q8mp8A+gpmweAbr0isR1/GKb7z61zUfrOaX9bN6CqydzI9Kjo9+SwPk1mObyJTFUsXdo9ca0+5g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR05MB6448
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-19_03:, , 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908190180
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/eGdd-VspRyOB9LYqiNxsWiboFxw>
Subject: Re: [Idr] Adoption call for draft-ketant-idr-rfc7752bis-01.txt [8/8 to 8/22]
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: Mon, 19 Aug 2019 17:02:15 -0000

Hi Sue & Authors,

As an implementor of RFC 7752, I support adoption of this draft as a WG document.

I have a comment on section 4.7, though.

Section 4.7 mandates withdrawal of link-state objects advertised by unreachable nodes. I’d suggest making this an optional behaviour of the originator. Originator not presuming consumer’s disinterest in certain entries would permit a wider range of applications.

If there is agreement that section 4.7 can be optional:

I don’t believe that the contents of section 4.7 merit a dedicated section. The last paragraph of section 1, reproduced below, offers plenty of leeway for an originator to choose what gets advertised. If this text is thought to be inadequate, an additional line or two in section 1 would suffice, IMHO.

“
A BGP speaker may apply configurable policy to the information that
   it distributes.  Thus, it may distribute the real physical topology
   from the LSDB or the TED.  Alternatively, it may create an abstracted
   topology, where virtual, aggregated nodes are connected by virtual
   paths.  Aggregated nodes can be created, for example, out of multiple
   routers in a Point of Presence (POP).  Abstracted topology can also
   be a mix of physical and virtual nodes and physical and virtual
   links.  Furthermore, the BGP speaker can apply policy to determine
   when information is updated to the consumer so that there is a
   reduction of information flow from the network to the consumers.
   Mechanisms through which topologies can be aggregated or virtualized
   are outside the scope of this document
“

--
Balaji Rajagopalan


From: Idr <idr-bounces@ietf.org>; on behalf of Adrian Farrel <adrian@olddog.co.uk>;
Organisation: Old Dog Consulting
Reply to: "adrian@olddog.co.uk"; <adrian@olddog.co.uk>;
Date: Friday, 16 August 2019 at 6:07 PM
To: 'Susan Hares' <shares@ndzh.com>;
Cc: 'idr wg' <idr@ietf.org>;
Subject: Re: [Idr] Adoption call for draft-ketant-idr-rfc7752bis-01.txt [8/8 to 8/22]

Hi Sue,

I’m a co-author on this draft.

I agree that an update to 7752 is needed. Sort of regret that we didn’t get this right first time. On the other hand, turning the handle and getting an RFC out was the right thing to do 3.5 years ago, and revising our work is a good demonstration that it is implemented and relevant.

So yes, I support adoption and hope we can spend as long as it takes getting this polished.

Thanks,
Adrian

From: Idr <idr-bounces@ietf.org>; On Behalf Of Susan Hares
Sent: 08 August 2019 20:31
To: 'idr wg' <idr@ietf.org>;
Subject: [Idr] Adoption call for draft-ketant-idr-rfc7752bis-01.txt [8/8 to 8/22]

This begins a 2 week adoption call for draft-ketant-idr-rfc7752bis-01.txt [8/8 to 8/22/2019]

In your comments please indicate “support” or “no support”.

The chair and AD feel that a revision to RFC7752 is needed
to specify additional error handling.  Please consider
if this draft is a good place to start for this revision.

Cheerily, Susan Hares