IETF Logo Mail Archive

Re: [pim] Issues with pim registers

"Vikas Ramesh Kamath (vikkamat)" <vikkamat@cisco.com> Thu, 26 April 2018 18:57 UTC

Return-Path: <vikkamat@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 48CF8127735 for <pim@ietfa.amsl.com>; Thu, 26 Apr 2018 11:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 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, T_DKIMWL_WL_MED=-0.01, 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
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 Z_qb5re93HJD for <pim@ietfa.amsl.com>; Thu, 26 Apr 2018 11:56:58 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4962D1200E5 for <pim@ietf.org>; Thu, 26 Apr 2018 11:56:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10964; q=dns/txt; s=iport; t=1524769018; x=1525978618; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Y5zUqZBmSoVwcW05zVBsv4A6CtTp3Va8T0+vsn5rRnw=; b=a8vUIW1tPSDHCSYgp14hXF+z1ovulNmwpv/7NJ6mUK/9a0f7O563BtmK ozqTDfGDPF1feYZUWpk5HQAJ/6VCfAiSW1+F0FHmWynu+zH8Eyodu5Jbf +jL7IyhSjO66hyG26/hTw1Ow0K2vKgrqE49zskmpa9XRqtj90GEQSdpRD E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BUAQCRIOJa/4UNJK1bGQEBAQEBAQEBAQEBAQcBAQEBAYJNRy9hF2MoCoNhiAKMeYMDjiOEcBSBZAsYAQqESQIagi4hNBgBAgEBAQEBAQJsHAyFIwIBAwEBIUsbAgEIQgICAiULJQIEARKEK2QPqDGCHB+EOYNvgkAFiBGBVD+BDyOCaIMRAQGBLQESAYMfMIIkAoc3iTqHGAgCjkaBNYNgh0CQFAIREwGBJAEcOGFxcBU7KgGCGIsQhT5vjn2BH4EYAQE
X-IronPort-AV: E=Sophos;i="5.49,331,1520899200"; d="scan'208,217";a="390134615"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Apr 2018 18:56:57 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w3QIuv8u028990 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 26 Apr 2018 18:56:57 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 26 Apr 2018 13:56:56 -0500
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1320.000; Thu, 26 Apr 2018 13:56:56 -0500
From: "Vikas Ramesh Kamath (vikkamat)" <vikkamat@cisco.com>
To: Stig Venaas <stig@venaas.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] Issues with pim registers
Thread-Index: AQHT2OBIdrcm6/bh202NfRRIHQv+1aQTwsIA
Date: Thu, 26 Apr 2018 18:56:56 +0000
Message-ID: <5E3BA7B3-F180-45B1-9A1D-10A3C9497888@cisco.com>
References: <CAHANBt+1=PYBDL-2M+jw4pyH_GGeoEzK1bK7_TcV7CRDbBtUBA@mail.gmail.com>
In-Reply-To: <CAHANBt+1=PYBDL-2M+jw4pyH_GGeoEzK1bK7_TcV7CRDbBtUBA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.131.86]
Content-Type: multipart/alternative; boundary="_000_5E3BA7B3F18045B19A1D10A3C9497888ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/P9-toDPBsCmarY1y9qvImFUnexQ>
Subject: Re: [pim] Issues with pim registers
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.22
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, 26 Apr 2018 18:57:00 -0000

Hello,



As part of draft-ramki-pim-null-register-packing, we have proposed a new standard for PIM NULL register and register stop messages. The motivation for this draft came from the issues seen in customer environments where the high number of PIM NULL registers were causing traffic drops.



We believe this new packet format will not only solve the above mentioned problem but also will help in optimizing bandwidth in the network by minimizing the number of NULL registers/register stops exchanged in the network. Please let us know your thoughts/feedback on this



Thanks,

Vikas



On 4/20/18, 12:46 PM, "pim on behalf of Stig Venaas" <pim-bounces@ietf.org on behalf of stig@venaas.com> wrote:



    Hi, I'm posting this as a WG chair.



    In the last meeting we had presentations of two drafts proposing

    alternatives or changes to the existing pim register mechanism, but we

    didn't have time to discuss them. The drafts were:



    draft-ramki-pim-null-register-packing

    draft-anish-reliable-pim-registers



    It would be great if people can provide comments on the drafts. I also

    think it could be a good start if we could have a discussion about

    what problems people are seeing today. What issues motivated the

    authors to propose these drafts, and what issues are other people

    seeing with the current pim register mechanism.



    I believe these mechanisms may also apply to pim anycast-RP, so issues

    with that could also be interesting to consider.



    I'm hoping this email can start some discussion. While I'm suggesting

    discussing pim register issues in particular, any thoughts people have

    would be more than welcome.



    Thanks,

    Stig



    _______________________________________________

    pim mailing list

    pim@ietf.org

    https://www.ietf.org/mailman/listinfo/pim

v2.23.0 | Report a Bug | By Email