Re: [pim] draft-ietf-pim-null-register-packing wglc
"Kesavan Thiruvenkatasamy (kethiruv)" <kethiruv@cisco.com> Thu, 06 February 2020 19:13 UTC
Return-Path: <kethiruv@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8EE712080A for <pim@ietfa.amsl.com>; Thu, 6 Feb 2020 11:13:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.397
X-Spam-Level:
X-Spam-Status: No, score=-14.397 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=RVnZj/Rb; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=r7B7V9gx
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 Xe4A0ZmW2ZLz for <pim@ietfa.amsl.com>; Thu, 6 Feb 2020 11:13:36 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76125120106 for <pim@ietf.org>; Thu, 6 Feb 2020 11:13:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=34949; q=dns/txt; s=iport; t=1581016416; x=1582226016; h=from:to:subject:date:message-id:mime-version; bh=D7/Dk2uTyQ0J9Vkx/VgSHsubAPYcOfsdi0GoTO2OXc0=; b=RVnZj/RbYK83Sa6jQS7uQFjkFC/QVN6BlN8qFr4PHQ7H+p1ae7u/Q11v zgN0YXsEYsq5tNslOKXKz75OsZdg5ltDC5u/kB4vVhDCL8umTrWUmF7z8 lMBSzoqevX3Sc6Q4H0OOskPs43DazCu7Qr6cY2sibjTG+QqBOlg5Jf7MW g=;
IronPort-PHdr: 9a23:nzUaYRwqkJOIWZfXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuGBFH7LeT3cQQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AdJwAqZDxe/4ENJK1mHgELHIMgLyQsBWxYIAQLKgqEC4NGA4p+ToFsJYlijjCCUgNUCQEBAQwBARgBCQsCAQGBKziCXQIXgiYkOBMCAw0BAQQBAQECAQUEbYU3AQuFZgEBAQEDAQEQER0BASwMEQEIEQMBAQEhBwMCBB8GCxQJCgQTIoJ/BAEBgX1NAy4BAgyiOAKBOYhidYEygn8BAQWBMwKBD4JsAwoLggwDBoE4hR+BLYFhg3YagUE/gTgMFIJMPoIbSQEBAgEZgWAJDQmCWjKCLI10IYJGhWKJfI5yRAqCOodKilGEKxuCSIgQhEiHJYRGjmKIbIIokA8CBAIEBQIOAQEFgWkiDYFLcBU7KgGCQRM9GA2NeSSDc4UUhT90AgEBAYEkjBEBgQ8BAQ
X-IronPort-AV: E=Sophos;i="5.70,410,1574121600"; d="scan'208,217";a="629228435"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Feb 2020 19:13:34 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id 016JDYOc030312 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <pim@ietf.org>; Thu, 6 Feb 2020 19:13:34 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 6 Feb 2020 13:13:34 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 6 Feb 2020 13:13:32 -0600
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 6 Feb 2020 14:13:32 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gM+hp6nZ3PtQMmhuMgUvQRHCfwavBaAVlvIFtu1V/1kObrpTFYFkMaV17mAMxIdAZohkFyWGl5gf0onnKXlb2PoPIZqQlZmTt1nnWjasZqS4pMRFOdE2MCrcs9hXErHQOszZfoX9+dCWrX5PuLuCjY4KtmQaXYcS56j25OrxQ/wpH0+S6LXs+g+Na4G2dems3zhJVqe7tI6TC4KpWrJanDztd9iJ9gVUCC3ckApp+RvmeTWm2whI6iV3IM8gIr5ovSmqvJAReK17ZP1LGq3FBWKAA4OAx0b28gya2rGZiQHAK7gT5doiWf2rBLDIX0Bz6kAwSc9SLdNNtxZLJBz/MA==
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=D7/Dk2uTyQ0J9Vkx/VgSHsubAPYcOfsdi0GoTO2OXc0=; b=hw2d/+Xl9sx3W+tFMkcRKulGxPhg+7uVoXK4dtw0Ublw5VHile1ex8sCkfJbgIBVatj+T2VYHss1tj8P8pPmoF6XXM21aZEJw1Du4sUposZdrJLvvDmvSD7DFIyj7VYp/ppS4/Pinu4K4Nsjjy0LEveSiFRPgBeY/yOrOLkP35VSTo86Mi5ZguLawmxXbBLpS6mkTCEKeY8aOIghZWqfEkGCA5R5ggLJyPDDGZPnTIHsC7JSWrT0yuIhGbQQYndPDWk0g709wZuDZEWUR3CPN51sCxio+/MUOHo2ELu0c1a6TRdpiH1bsjK1aCn6yj2e1t0q+7roB+58bDRsm/RbDw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=D7/Dk2uTyQ0J9Vkx/VgSHsubAPYcOfsdi0GoTO2OXc0=; b=r7B7V9gxtnUHEjG1ar7LBXxKfzpJHBQ7EMITD0J+lCLhqLQ3/L1PKFLFtr+Ob0865k7Q1ygkXSkYyHOjXWjBg/ryQurbLMj01qYQwvTzyUpiIN/SLjvcM3dcd5JUovzcO9DUHvsrzF2J/9YAMxCumJGjltdF/+Do1KCxaj1H478=
Received: from BYAPR11MB3464.namprd11.prod.outlook.com (20.177.184.205) by BYAPR11MB3480.namprd11.prod.outlook.com (20.177.127.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.21; Thu, 6 Feb 2020 19:13:31 +0000
Received: from BYAPR11MB3464.namprd11.prod.outlook.com ([fe80::cd01:2e36:e71e:452e]) by BYAPR11MB3464.namprd11.prod.outlook.com ([fe80::cd01:2e36:e71e:452e%6]) with mapi id 15.20.2707.024; Thu, 6 Feb 2020 19:13:31 +0000
From: "Kesavan Thiruvenkatasamy (kethiruv)" <kethiruv@cisco.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] draft-ietf-pim-null-register-packing wglc
Thread-Index: AQHV3SGEFpThSLqzO0umJWJByMB1UA==
Date: Thu, 06 Feb 2020 19:13:31 +0000
Message-ID: <661EF54B-A98D-4579-931F-8CCA4CF283F9@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.21.0.200113
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kethiruv@cisco.com;
x-originating-ip: [128.107.241.167]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c8a449bd-ec99-4052-465f-08d7ab38a772
x-ms-traffictypediagnostic: BYAPR11MB3480:
x-microsoft-antispam-prvs: <BYAPR11MB348027E312A1A364147E3D1DCA1D0@BYAPR11MB3480.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0305463112
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(39860400002)(346002)(396003)(376002)(189003)(199004)(2616005)(6916009)(186003)(26005)(53546011)(6506007)(36756003)(33656002)(8676002)(81156014)(81166006)(8936002)(2906002)(66574012)(71200400001)(6486002)(6512007)(66946007)(966005)(66476007)(66556008)(478600001)(66446008)(64756008)(5660300002)(316002)(86362001)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3480; H:BYAPR11MB3464.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: c9iQcExogitVuU4wDgaYVodjZWhSkkkd8kTx9eGf+BzqeoFgqaJE28yvyus8RUEPEqkFmQXth/K6eQlMbiQ02DeEAcsZU3eHEYKwNUnNeTpdzPJCAXL3VvOSnWEmU5uB58JoZoK1/owOcGUO3Wi7vYUsR3aK5n84c5FBY1L5QCq50uKZWZyZMDfSjKoLssdWwILWuoTZQQzdeBrfdV1fPVPCVoBSCeQSYiCwW08ythaQZV5nD0/5frTBvFjE1H2rSGRsQfGMAqUzJ/fNjdq82MfTVxQHPrHzsTr6wYfweSXW4aBgwDbdLtie7U2qtKW3aY6XQ4C5aRflqaCbZKmBmm3aN8QvKnQovm+t2jc89xRE1tI6I0/9KsfZ1mKji5jiJTlBby1IMvO+3dlqoDxC+0F9T/WtHGm/HtQ40yalvpMyOO27uX1UG6qZpE14eK49cARa+Kq/9DpWj+hXZ6MGIjSh/n7kmq98O2vdUhlTCzvWU8/QLfiaM35HDFQYErcsMBibr48DF7RM0PZn/yxpEA==
x-ms-exchange-antispam-messagedata: UFPixa+EGlA6ABhrWdx2v5DFy8W3hGKGRkEkexwt0XnTSNN5OoM+xkKinkoZWDEMoPFEjCq90kpofdFR3893Ph8585Xa4HlELQ4lv8J8oVKj3WMOzozPvFrYUbTFzrP7Jzy2zOjSf0YgdlDJoDiAjA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_661EF54BA98D4579931F8CCA4CF283F9ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c8a449bd-ec99-4052-465f-08d7ab38a772
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Feb 2020 19:13:31.0198 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rD9M+gsLnafCRmUKsUPyGhoZrna42HGebBEif5o3V5W+hsy32Oq1wUh2FKWv+lpclhGXslzJrfAhQJdEL3+u0A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3480
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/OYLiRrowqw4UMH1LmEsYdn99qRU>
Subject: Re: [pim] draft-ietf-pim-null-register-packing wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2020 19:13:40 -0000
Support. Regards, Kesavan From: pim <pim-bounces@ietf.org> on behalf of Michael McBride <michael.mcbride@futurewei.com> Date: Thursday, January 30, 2020 at 4:40 PM To: "pim@ietf.org" <pim@ietf.org> Subject: [pim] draft-ietf-pim-null-register-packing wglc We are going to start a new wglc for https://www.ietf.org/id/draft-ietf-pim-null-register-packing-04.txt which was updated based upon comments during the first wglc (please see below). Since we received only one comment, and really no one showing wglc support, we are issuing a new wglc. Sometime over the next two weeks please let the wg know if it’s ready to be sent to the iesg for publication. thanks, mike From: pim <pim-bounces@ietf.org> On Behalf Of Ramakrishnan Chokkanathapuram (ramaksun) Sent: Tuesday, October 15, 2019 11:37 AM To: Anish Peter <anish.ietf@gmail.com>; Mike McBride <mmcbride7@gmail.com> Cc: pim@ietf.org Subject: Re: [pim] draft-ietf-pim-null-register-packing wglc Hello Anish, Thanks for the comments.. I have my responses inline.. Thanks, Ramki From: pim <pim-bounces@ietf.org<mailto:pim-bounces@ietf.org>> on behalf of Anish Peter <anish.ietf@gmail.com<mailto:anish.ietf@gmail.com>> Date: Wednesday, September 4, 2019 at 7:20 AM To: Mike McBride <mmcbride7@gmail.com<mailto:mmcbride7@gmail.com>> Cc: "pim@ietf.org<mailto:pim@ietf.org>" <pim@ietf.org<mailto:pim@ietf.org>> Subject: Re: [pim] draft-ietf-pim-null-register-packing wglc Hi all, Read through the draft. Have a few comments. 1. Section 2: The P bit can be taken as the LSB on the reserved ones. This would help this get inline with recommendations from PIM draft-ietf-pim-reserved-bits. ##Ramki## Not sure if using LSB or MSB has an advantage here. I am not sure if the pim-reserved-bits mandates such thing. 1. Instead of taking two new pim message types, the same pim register and register stop messages may be used. if this procedure can be followed. ##Ramki## It will be good to have a new type. If we overload the same type it could happen that a router receives a message and think its malformed. a. RP discovers FHR capable of register bulking from the P bit. b. When RP responds to this register, it can set set a P bit in R-S message. c. Once FHR knows peer has bulking capability it can register packets with bulking d. For bulked register messages, RP can respond with bulked R-S messages. e. Packet format. I suggest overloading existing register and R-S packet can be done with out using two new packet formats. Register 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |PIM Ver| Type | Reserved | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |B|N|P| Reserved2 | S-g-count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | . Multicast data packet . | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Register-stop 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |PIM Ver| Type | s-g-count |P| Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Group Address (Encoded-Group format) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source Address (Encoded-Unicast format) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3. Anycast RP In my opinion, anycast RP procedures must be defined. Protocols typically should not ask for any kind of specific configurations or features on its peers. ##Ramki## PIM Anycast RP is based on configuration. So not sure if this is a problem. 4. Restart / feature disable An RP/FHR may restart or may have bullking turned on/off. In these scenarios the behavior must be defined. ##Ramki## Yes. In such scenarios if an RP is downgraded from a version that was supporting packing to one that doesn’t support it, then RP will not respond to the packed registers. In such cases one could send an unpacked register to RP to check if the RP supports it or fallback to data register and then discover the RP capability. Thanks, Anish On Thu, Aug 29, 2019 at 6:58 AM Mike McBride <mmcbride7@gmail.com<mailto:mmcbride7@gmail..com>> wrote: PIMers, Today begins a two week wglc for draft-ietf-pim-null-register-packing which was presented at 105 and hasn't changed since April. Please give it a read (it's a quick read) and provide feedback to this wg with support/no support of it's progressing to iesg. thanks, mike https://tools.ietf.org/html/draft-ietf-pim-null-register-packing-03<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-pim-null-register-packing-03&data=02%7C01%7Cmichael.mcbride%40futurewei.com%7Cc817a6aa05fd4fc3f50208d7519eb3d6%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637067614378147075&sdata=U4DlCfyCEacllFZQ6Hi8pIqzwhRvy2N2P2OcjYRRX9A%3D&reserved=0> _______________________________________________ pim mailing list pim@ietf.org<mailto:pim@ietf.org> https://www.ietf.org/mailman/listinfo/pim<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fpim&data=02%7C01%7Cmichael.mcbride%40futurewei.com%7Cc817a6aa05fd4fc3f50208d7519eb3d6%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637067614378147075&sdata=NAHGy5MAsL4MB9XT%2Bw2pEfegIgTkOYRm4dFbqtnDpwI%3D&reserved=0>
- [pim] draft-ietf-pim-null-register-packing wglc Michael McBride
- Re: [pim] draft-ietf-pim-null-register-packing wg… zhang.zheng
- Re: [pim] draft-ietf-pim-null-register-packing wg… Jeff Tantsura
- Re: [pim] draft-ietf-pim-null-register-packing wg… Kesavan Thiruvenkatasamy (kethiruv)
- Re: [pim] draft-ietf-pim-null-register-packing wg… Michael McBride