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

phani Ayyappa <durgam.iit@gmail.com> Wed, 26 July 2017 09:43 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 7DAF71318A8 for <pim@ietfa.amsl.com>; Wed, 26 Jul 2017 02:43:17 -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 g3ZmDrkPfc8x for <pim@ietfa.amsl.com>; Wed, 26 Jul 2017 02:43:16 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 17DA61318A2 for <pim@ietf.org>; Wed, 26 Jul 2017 02:43:16 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id k71so75690501wrc.2 for <pim@ietf.org>; Wed, 26 Jul 2017 02:43:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=k6Ex4l9MIQbxlqGK0AnC53rbfAjr7iTKd6q2XNixZ7A=; b=LnyUHg2yoRWx9ANY+3lZw+sAM4SCQ7Y6z/JjAnfZwrwYbTkCaiaIL4VtAjvl97UJA9 7w/+bKOxMX3+GlGfTVc5OZhSeAB5Drnf8AKrynSCUkO98czAqV3hf+4/31an6ya5fpE7 bKMuHKEVzsZrYVnrQuTYPVKKkBGXSDtU9gNGVzfSbmRhltoHFItf2u5wMxb5o76Lmcba 6RD3wxlcMoAzhnGAK4+y9T6ptEYBXCWP4YbzxoC9OTto2WVRuypU1+RFo62KTynXwzYI s2RSn1fWnAmS+3/IeWhPV31aEAH05mHmE3n0xTJt4FmdGXKKpaVuy4vJR8kf0KddOpJ1 pK5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=k6Ex4l9MIQbxlqGK0AnC53rbfAjr7iTKd6q2XNixZ7A=; b=LCc5lF+w4o4YCQBMS5lUpR9ZkQRi2q5UVwC5ym6AywOaa5XyU2koItTt8cOJ0Ik5Ax w/pyFkIuHRQ9FLMed150ZNviPeBdZ5/qf5xwhvdallA9FyjfZJRYyj4ZzwUYAZPDz39W XyBpnOQXCSXWd6CtfIdkNeg/TBs1GjQUm++y0Vz62AGE1WL6n+XxL7xnOkoEpnN6qeou EiggxJ9CO9K7Zw2KZV0bAVLDR65sBa2OaD9tmCsrJ+ilSKPg7s8fT5+y8YVHcrJl2gAr 0ZqjwCkCqN5GffpckfebepN+aWCJdl1AMfJjZuyFM8vKRZTFyxCtiq8eSOAgDVEP6JQm o04g==
X-Gm-Message-State: AIVw112DdQ35RWChOMu3hnobi+yKNnzTSqv7UxXDdr8yJ/RI7wLSt8as Q3lT3retqeBkHfOV67+3tqYBKwovn2/X
X-Received: by 10.223.134.39 with SMTP id 36mr389269wrv.244.1501062194464; Wed, 26 Jul 2017 02:43:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.139.24 with HTTP; Wed, 26 Jul 2017 02:43:14 -0700 (PDT)
From: phani Ayyappa <durgam.iit@gmail.com>
Date: Wed, 26 Jul 2017 02:43:14 -0700
Message-ID: <CALXDUZi4JzLJKB5RaKi87HmW1Pevwrx1ECr9skxVRMEowoCdLA@mail.gmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary="001a1146c380e310500555354638"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/M8i_HPq75it-KCUqGwlJ0ZIIm3g>
Subject: [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 09:43:17 -0000

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