Re: [pim] regarding creation of (s, g) state in pim ssm on FHR
"iamredheart22 ." <myselfindranil@gmail.com> Wed, 26 July 2017 12:47 UTC
Return-Path: <myselfindranil@gmail.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 BC23A131C8E for <pim@ietfa.amsl.com>; Wed, 26 Jul 2017 05:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 nBVPKDmPozY9 for <pim@ietfa.amsl.com>; Wed, 26 Jul 2017 05:47:02 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C0F0129ACD for <pim@ietf.org>; Wed, 26 Jul 2017 05:47:02 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id m85so66554095wma.1 for <pim@ietf.org>; Wed, 26 Jul 2017 05:47:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZoR9Q9qfpOiHEADHuaEb0OgdseuD3Yc1lAm4TjXcAd4=; b=cPNO1GYrAn+yEwcjmajANlV2Dp75eFq/4Gj/LDmsxrZc8CdWLgEwi0ahRlIUvW6UUW eg1AHDph+axRS1DIG8/7jLhFoJYzsWGOU9svTzDLVAP9Zr0mf7nq1iz8QwRJJGPKwoOM O7Jnp+8LB4KLuBCwAdk7vHMRjl3SS3jzn1maRexl7MuwhEWkzAGGE/JgxQTlB2tT70XQ EhClmPYk4Qq4opl+/XPaECr8MlMcZQnaZR2EfPDINt4WVXiu5c1SMIxKZHHsq5zAZ5QS AwAOW4CAmLWm0WT+UwexHxJwrC9jUyxLe2fqxNmN2pRGM17yNTtIwwLSaA1UJJGOkV8b tfIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZoR9Q9qfpOiHEADHuaEb0OgdseuD3Yc1lAm4TjXcAd4=; b=ITWflZunTGM94Bk0twyscNzJ8s8kXLUMc/KC7PZypoxTarERGQiMBjsNByZv8PAcjc zGkzytoF8GgZj1g/hBLGD55HCGSRTOfUbCrq3408VX5GGlnfhYoYxNTEpwIKbVqzvn7e 72rx3T+uq2C59tbmSKqzbB9cyoAsi26NU6Vt2QX2Sq4I9rEmHOdn2ugY5yxoSiGfjwLV HFPPDbjgkGDl8JJa4yyToUGOXWlq7kWHACC/GtceQk5MjzzB6mXbab0kfTRUhW3jVmax D8dnIbVgX2uZ7wREiW97dJ1qXcrTrKc9neSvKe1Cl/7uJ3pTeeYu1yF5PUYmXWQVQLLK ZpaQ==
X-Gm-Message-State: AIVw110bdfCPdMVQ3c4eMFNVeMxOKrnnVHZE5bCidAEEJYQ6Fmlz7U49 E8QRPzFhyHwgGHGN4P9m+FeF27Iqow==
X-Received: by 10.28.46.197 with SMTP id u188mr664413wmu.26.1501073220987; Wed, 26 Jul 2017 05:47:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.44.68 with HTTP; Wed, 26 Jul 2017 05:47:00 -0700 (PDT)
In-Reply-To: <CALXDUZi4JzLJKB5RaKi87HmW1Pevwrx1ECr9skxVRMEowoCdLA@mail.gmail.com>
References: <CALXDUZi4JzLJKB5RaKi87HmW1Pevwrx1ECr9skxVRMEowoCdLA@mail.gmail.com>
From: "iamredheart22 ." <myselfindranil@gmail.com>
Date: Wed, 26 Jul 2017 18:17:00 +0530
Message-ID: <CAAaur97Xk4LgEJe1P0AAND_+v-KK7H+LaccT7-s1Jd0fUbReow@mail.gmail.com>
To: phani Ayyappa <durgam.iit@gmail.com>
Cc: "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary="001a1142297c1e8b6b055537d828"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/lHsFJxIL1kgERnZ9T4P3uKEIgiE>
Subject: Re: [pim] regarding creation of (s, g) state in pim ssm on FHR
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: Wed, 26 Jul 2017 12:47:05 -0000
Hi Pani,
Yes it is mandatory to create and keep the (S,G) state on FHR so
that periodic NULL register packets keep the the (S,G) state on the RP
alive. Otherwise, how else do you restart the traffic when the receivers
join? Are you using BSR based source signaling or something similar?
If the group falls in SSM range then no need to create (S,G)
state from data.
Thanks,
Indranil
On Wed, Jul 26, 2017 at 3:13 PM, phani Ayyappa <durgam.iit@gmail.com> wrote:
> Hi,
> Does first hop router needs to create (s, g) state on the router, though
> there are no interested receivers present down stream ? Does RFC mandate
> creation of (s, g) state in this scenario ?
>
>
>
> Thanks
> Pani
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>
>
- [pim] regarding creation of (s, g) state in pim s… phani Ayyappa
- Re: [pim] regarding creation of (s, g) state in p… phani Ayyappa
- Re: [pim] regarding creation of (s, g) state in p… iamredheart22 .