IETF Logo Mail Archive

Re: [pim] regarding creation of (s, g) state in pim ssm on FHR

phani Ayyappa <durgam.iit@gmail.com> Wed, 26 July 2017 10:21 UTC

Return-Path: <durgam.iit@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 C22E9131C2D for <pim@ietfa.amsl.com>; Wed, 26 Jul 2017 03:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 xhY350Hp5LCe for <pim@ietfa.amsl.com>; Wed, 26 Jul 2017 03:21:50 -0700 (PDT)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (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 C2EB3129B7A for <pim@ietf.org>; Wed, 26 Jul 2017 03:21:49 -0700 (PDT)
Received: by mail-wr0-x22c.google.com with SMTP id v105so99399838wrb.0 for <pim@ietf.org>; Wed, 26 Jul 2017 03:21:49 -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=7RYqvf9Wsto4LcnWmT0U8k19YP2VEl8OCAQy1w82Gak=; b=d4nMlHj6LxwltaHlwnCxKAu4wJzI3vw9028n7E+ZRiubEYkv0GlGsX3vOQWzxMRo3y kq2O3NbG6oZtpGxIwYNnVrcHs8kLARVb87S1hYBHTZF2r//p6a0YgD5+Osvlu9/b4lNN Cm7FnfoxWSgYfjBF75SUpcUKxXzjrWOAqcioePjmPqX7D4yAHu75V7JlWZJCsoYLVe72 lvP8CyRKoA/T5SpQZ+i908Eo9H046ftJN46e5Mr9VFoXT/hgJbwpsWnL/R6E2j2GsD4A louhwnCs/vJSc09DUFSnwL/M6ZIGN4j/TXwFR0rzAH0qN1R/Jb5vopwNEMwKIC2Fvfhk lnUg==
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=7RYqvf9Wsto4LcnWmT0U8k19YP2VEl8OCAQy1w82Gak=; b=aTUwF957qYJ8z4pv8WzP2F0S+ur9GcWnRzCYDukNvMaQDq1MxU9RXKba5MDaWdJLVn kAlfjBiDVb6NYkqkiwN0n5isdb09yF60RRyNgch41df5XOe3qKh8591W/fP/X6IntOZd 1Y91kUjOTpqtPUfSjoFO3d8uY6pKT/kVNGWPR+1978RdVnKt1mN31sAzAV0L9QHFfLtk KruuaQoas4NqUE+5OTSZcXBpDf4tvNqyvDgHPSqjG/bh+dZ/iyANLNyDi9EjjvN1IcpG 4VVmBhvRalXlGitJ4Q/xO+gjhYLZB7F7c0EYQxYQEi29eBNKdJmllMMk5Fuo+Z7GztLQ j4uQ==
X-Gm-Message-State: AIVw111UDXqnMDw9RGlPO7Uq906paSy/8Z0mBu4gRQJzOKfwzMvAQJfG 1fX20jEqoZzx4fcGRQ80dWvssbzxig==
X-Received: by 10.223.145.162 with SMTP id 31mr482206wri.171.1501064508254; Wed, 26 Jul 2017 03:21:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.139.24 with HTTP; Wed, 26 Jul 2017 03:21:47 -0700 (PDT)
In-Reply-To: <VI1PR07MB14869DC8196D1BCE74C9A0E39AB90@VI1PR07MB1486.eurprd07.prod.outlook.com>
References: <CALXDUZi4JzLJKB5RaKi87HmW1Pevwrx1ECr9skxVRMEowoCdLA@mail.gmail.com> <VI1PR07MB14869DC8196D1BCE74C9A0E39AB90@VI1PR07MB1486.eurprd07.prod.outlook.com>
From: phani Ayyappa <durgam.iit@gmail.com>
Date: Wed, 26 Jul 2017 03:21:47 -0700
Message-ID: <CALXDUZiF0hH8Cd2BDGEpfEKqMdTrcDS8e1Thj8O7GiucgEE26w@mail.gmail.com>
To: "V, Magesh (Nokia - IN/Bangalore)" <magesh.v@nokia.com>
Cc: "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0df140ccae83055535d0b9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/0kX_T9SHI-4051GxA15FDFAufIE>
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 10:21:52 -0000

Hi Magesh,
 Does this state (s, g) is needed , when this group range falls in ssm
space ?

Thanks
Pani

On Wed, Jul 26, 2017 at 3:17 AM, V, Magesh (Nokia - IN/Bangalore) <
magesh.v@nokia.com> wrote:

> Yes, I believe so.
>
> FHR creates (s,g) state and does an encapsulated forwarding of traffic to
> the RP. RP responds with ‘Register-Stop’ message back to FHR if there are
> no active listeners. The (s,g) state on FHR will remain as long as the
> traffic is hitting the node; however, its OIL might be null (or maintained
> as register_interface, not 100% sure here).
>
> Thanks,
>
> Magesh.
>
>
>
> *From:* pim [mailto:pim-bounces@ietf.org] *On Behalf Of *phani Ayyappa
> *Sent:* Wednesday, July 26, 2017 3:13 PM
> *To:* pim@ietf.org
> *Subject:* [pim] regarding creation of (s, g) state in pim ssm on FHR
>
>
>
> 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
>

v2.23.0 | Report a Bug | By Email