Re: [pim] draft-ietf-pim-null-register-packing wglc

"Ramakrishnan Chokkanathapuram (ramaksun)" <ramaksun@cisco.com> Tue, 15 October 2019 18:37 UTC

Return-Path: <ramaksun@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 672D712007C for <pim@ietfa.amsl.com>; Tue, 15 Oct 2019 11:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_HI=-5, SPF_PASS=-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=YeuQUd1S; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=JDZ8qh7p
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 Hre1q1Da6XvS for <pim@ietfa.amsl.com>; Tue, 15 Oct 2019 11:37:07 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 014451200FF for <pim@ietf.org>; Tue, 15 Oct 2019 11:37:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27651; q=dns/txt; s=iport; t=1571164626; x=1572374226; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/53MvD0TMd3a7ZOpXQx2WhINmzF0ie+aX15QeB2NJq8=; b=YeuQUd1S/6XcRJFBxab6v0cJ4k0+gQa9taSl7UAw+01/xwTikg7RKZC1 5t8ZXUm4fViYNtG0Mk4HTb70I/wiM1jwg6J9J2NLEK+0eKKmUkF+6skl9 xoIjfu/tgsZtenAdL5/IPX1+CEMHFmaUms2VM/hejbbkdJrrTntIHC6qp 0=;
IronPort-PHdr: =?us-ascii?q?9a23=3AAn9h2RzJxiFrQwHXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZufAEjyL+X3aQQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DXAADUEKZd/4cNJK1mGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF7gRwvJCwFbFcgBAsqCoQbg0cDik6CNyWJao4?= =?us-ascii?q?UglIDVAkBAQEMAQEYAQoKAgEBgSuDFQIXglckOBMCAwkBAQQBAQECAQUEbYU?= =?us-ascii?q?tDIVLAQEBBAEBEBEdAQEsCwEPAgEIEQMBAiEHAwICAh8GCxQJCAIEAQ0FIoM?= =?us-ascii?q?AAYF5TQMuAQIMo30CgTiIYXWBMoJ9AQEFgTgCgQ+CQA0LghcDBoE0hRWBKoF?= =?us-ascii?q?ag3UYgX+BOAwTgkw+ghpHAQEDgXUJDQmCWDKCLI06gjeFOZdkQQqCIocKigm?= =?us-ascii?q?ECBuCOodPhCyLDY4xiCOCD48JAgQCBAUCDgEBBYFpIoFYcBU7KgGCQVAQFIF?= =?us-ascii?q?Pg3OFFIU/dIEpjwsBgSIBAQ?=
X-IronPort-AV: E=Sophos;i="5.67,300,1566864000"; d="scan'208,217";a="644346440"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 Oct 2019 18:37:05 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x9FIb5wo023567 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 15 Oct 2019 18:37:05 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 15 Oct 2019 13:37:05 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 15 Oct 2019 14:37:04 -0400
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 15 Oct 2019 13:37:03 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ads7YvaEQxVLSeHfLYglgWpzWSd8QxDBzGALceK5940BSvqLUBiij1/9T4RSLVXvylA5TqnhPGLaq8uzqTaDf7d9UKGGYnkTHFUR0ccooWh/E4FUYZ2zmUzCXa7Tj/VmR2Eu9M1pNQRlhmAGccGMvSp6KVT0Qts64WxfLFLE1De9ac+6tucmkJh1P+MUYXgSn0qh+5o8374KWv/lF2aVXX4wODPbt7GB+2V8R10vxnS7QYbgp8/vGqCO2wGdmGxsKgqeMAN2bsfK9N170xew4tGvzSCQXftd5pi6Qg/PTfbMjJOtqRP1C+TjkYHzCQ38CMYREU1Zin8xp7tykYS+xg==
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=/53MvD0TMd3a7ZOpXQx2WhINmzF0ie+aX15QeB2NJq8=; b=J6oOOXes1AYMLJinlorOXeSJjdgcZs45UfgtVi6GtJMUir9VABM1Du5BqJ6yBndspdzCvX0vBzxWCSHAkQRNcyz2qEGXcNbJ19HlWmRUO/psjhqixi9JN6gde5K/EL0xfpTW6++j/KWzClUIm36N2/sEsw2JkzhsWvCpRQG0SYo9Ft1sukGRhc7Xv8dzCeLbIAu/RvCNAKE++X5a5mqliLcFZsyEWfhWT8wzbqFE9K73gRoLAYl0t+y58PBBpLod2u4HsTR+Zy1HZgr+ScLKLSbqdvQDfLAc4GOeP2Y1ZOSkMpcmiYOKlGF7Ap7JH3wqM9WQ+iBDa7b7D6cV3ehogA==
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=/53MvD0TMd3a7ZOpXQx2WhINmzF0ie+aX15QeB2NJq8=; b=JDZ8qh7pbrTmXIAeznIYyZtDj/yT8EODgvEY3q7OEMWFIj5Jln28QvItgQgEScn1y4s90K6bKrdmp174MJGvzQ7z+Asu5COIbD/kByfFD1k6GRrd7LQ/d85ZrgNG/w/1p5CIACi2UOCdQF5M4ym8hWs/9bNk/gE0+5IxuXmSDa4=
Received: from DM6PR11MB3067.namprd11.prod.outlook.com (20.177.218.152) by DM6PR11MB2780.namprd11.prod.outlook.com (20.176.100.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.16; Tue, 15 Oct 2019 18:37:03 +0000
Received: from DM6PR11MB3067.namprd11.prod.outlook.com ([fe80::995:7c28:936:9a3c]) by DM6PR11MB3067.namprd11.prod.outlook.com ([fe80::995:7c28:936:9a3c%4]) with mapi id 15.20.2347.021; Tue, 15 Oct 2019 18:37:03 +0000
From: "Ramakrishnan Chokkanathapuram (ramaksun)" <ramaksun@cisco.com>
To: Anish Peter <anish.ietf@gmail.com>, Mike McBride <mmcbride7@gmail.com>
CC: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] draft-ietf-pim-null-register-packing wglc
Thread-Index: AQHVXgkYm1UNJQHTnEOw1U9nVAeOqKcbm3oAgEBCLQA=
Date: Tue, 15 Oct 2019 18:37:02 +0000
Message-ID: <4AED57D9-3BB3-4099-9564-8F2EF917FA5E@cisco.com>
References: <CAL3FGfyC32VB2xw0AM7Btc4UJ-oVGw26sa8ZgmK35QzpHOzESQ@mail.gmail.com> <CAA6qS9rX5uCiDh1NauBfUjCb3mEd-=_PeviHPxehYUPF7oVb4w@mail.gmail.com>
In-Reply-To: <CAA6qS9rX5uCiDh1NauBfUjCb3mEd-=_PeviHPxehYUPF7oVb4w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ramaksun@cisco.com;
x-originating-ip: [128.107.241.183]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4f2a7548-4b6b-43be-4942-08d7519eac34
x-ms-traffictypediagnostic: DM6PR11MB2780:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DM6PR11MB27803A21E35779B97B1FABCBDC930@DM6PR11MB2780.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 01917B1794
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(396003)(366004)(346002)(376002)(39860400002)(53754006)(199004)(189003)(51914003)(102836004)(99286004)(6116002)(7736002)(26005)(186003)(6506007)(76176011)(256004)(446003)(486006)(71190400001)(476003)(2616005)(11346002)(71200400001)(53546011)(2906002)(3846002)(66066001)(25786009)(14454004)(606006)(478600001)(66476007)(6436002)(110136005)(58126008)(64756008)(66946007)(316002)(86362001)(91956017)(76116006)(66556008)(66446008)(4326008)(236005)(6512007)(54896002)(6306002)(36756003)(6486002)(9326002)(229853002)(8936002)(6246003)(33656002)(8676002)(81156014)(81166006)(66574012)(5660300002)(966005); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB2780; H:DM6PR11MB3067.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: dUpCBurqV9ABVj7tbyFJGqrHGG81Oz0ExMktwZ3lTlH3wckc8CBL913dnO27pV8lJM+LjS8FpAjiDEUkZeY15AzDSWO8yGSo1npmp9NCvcP3gz2pa6BKJCuY3HAPxDx8i/nKV7Hb9idqkcOD8++kPWlg5XD5D35XLCTY6UQpqaZ3X3UITiRIPZKogkxJlAaGpdNeX6ZDjzGwXiTlcyO2atk9niGQwAP9AGyL7OcAfXRek9rXf1smPyAduH34eqKPnPjPInpibTz7ueAL4UP7ESnNj1H1E3/taLE6z76sLHXtqM360w1H82g+ZNNxjN8Dg/6P79tnZOSjwHg3XbkfQK00/2o/dwlILhOlz4K8M8clymN3x19Nvt17uQwug02qGpV9t75qf1FGRAnk4kLM9HXBDskwaqePhvH4sD3Jj4o/4m2t97fQXD6ypHUEGBsA55TvXK4Iw66xyKvIZdq7/w==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_4AED57D93BB3409995648F2EF917FA5Eciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4f2a7548-4b6b-43be-4942-08d7519eac34
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Oct 2019 18:37:03.0195 (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: 0MkHkTlaGZLi/GBpwSOzA/7oXNmeJFZ0/4gSVobrJ3Y/FYnzpwaarhiJTvfrxg0UUOmcnOeMeqijg5BMzR2KyQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB2780
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.24, xch-aln-014.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/AJwwfjl9upq4iIBzGDL2e-NVdlM>
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: Tue, 15 Oct 2019 18:37:09 -0000

Hello Anish,

Thanks for the comments.. I have my responses inline..

Thanks,
Ramki

From: pim <pim-bounces@ietf.org> on behalf of Anish Peter <anish.ietf@gmail.com>
Date: Wednesday, September 4, 2019 at 7:20 AM
To: Mike McBride <mmcbride7@gmail.com>
Cc: "pim@ietf.org" <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

_______________________________________________
pim mailing list
pim@ietf.org<mailto:pim@ietf.org>
https://www.ietf.org/mailman/listinfo/pim