
From nobody Tue May  6 20:41:56 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEF01A021D; Tue,  6 May 2014 20:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 FPHKjM06tx3K; Tue,  6 May 2014 20:41:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A39EB1A020F; Tue,  6 May 2014 20:41:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140507034151.13025.40438.idtracker@ietfa.amsl.com>
Date: Tue, 06 May 2014 20:41:51 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/uJmylIh4iJnNliNhVx3pdVxcd8Y
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-rfc4601bis-03.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 07 May 2014 03:41:53 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

        Title           : Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)
        Authors         : Bill Fenner
                          Mark Handley
                          Hugh Holbrook
                          Isidor Kouvelas
                          Rishabh Parekh
                          Zhaohui (Jeffrey) Zhang
                          Lianshu Zheng
	Filename        : draft-ietf-pim-rfc4601bis-03.txt
	Pages           : 133
	Date            : 2014-05-06

Abstract:
   This document specifies Protocol Independent Multicast - Sparse Mode
   (PIM-SM).  PIM-SM is a multicast routing protocol that can use the
   underlying unicast routing information base or a separate multicast-
   capable routing information base.  It builds unidirectional shared
   trees rooted at a Rendezvous Point (RP) per group, and optionally
   creates shortest-path trees per source.

   This document addresses errata filed against RFC 4601, and removes
   the optional (*,*,RP) feature that lacks sufficient deployment
   experience.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-rfc4601bis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-rfc4601bis-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-pim-rfc4601bis-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon May 19 11:30:18 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 618881A01DD for <pim@ietfa.amsl.com>; Mon, 19 May 2014 11:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.954
X-Spam-Level: **
X-Spam-Status: No, score=2.954 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FRT_BELOW2=2.154] autolearn=no
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 EAaRQToVWcXa for <pim@ietfa.amsl.com>; Mon, 19 May 2014 11:30:14 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC2B1A02C8 for <pim@ietf.org>; Mon, 19 May 2014 11:30:14 -0700 (PDT)
Received: from [10.154.208.71] (128-107-239-235.cisco.com [128.107.239.235]) by ufisa.uninett.no (Postfix) with ESMTPSA id A27AA8037; Mon, 19 May 2014 20:30:12 +0200 (CEST)
Message-ID: <537A4DB2.4040903@venaas.com>
Date: Mon, 19 May 2014 11:30:10 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: saeed sami <sami.biz.email@gmail.com>, pim <pim@ietf.org>
References: <CAJeqxZmD1LJbmH5zn6PDzBOGZ+pNNjzmdKHQW9X1FSWGmKiSMQ@mail.gmail.com>
In-Reply-To: <CAJeqxZmD1LJbmH5zn6PDzBOGZ+pNNjzmdKHQW9X1FSWGmKiSMQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/y2TErnIjDDQpAzZZsV583KajOlU
Subject: Re: [pim] New updated and edited version of draft-sami-pim-ng (part 2)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 May 2014 18:30:17 -0000

Hi

Sorry for the late response, let me comment on this.

On 4/29/2014 3:54 PM, saeed sami wrote:
> Dear Mr.Venaas,
> Hello
> First of all let me thank you for your review, comments and the time you
> have
> dedicated to review my work "draft-sami-pim-ng-02".
>
> http://tools.ietf.org/html/draft-sami-pim-ng-02
>
> Since answering to your questions will be a little lengthy and cant be
> posted to PIM mailing list as a single email, i have to post them in
> separate  parts. and this is part 2.
>
> Please kindly find the answers and explanations to your questions and
> doubts bellow. i hope that as you mentioned in your email there will be
> more comments from other members after this.
>
> The answer to your questions are as follows which I hope will be
> satisfying:
>
> *1- Source register process  in PIM-NG and its similarity to PIM-SM:*____
>
>
> At the first glance the overall register process may seem similar to
> PIM-SM, but
> the register process in PIM-NG is different from PIM-SM. Bellow the
> process is
> briefly explained to make it clearer:____
>
>
> -  Source sends a unicast-encapsulated register message to the address
> of the
> RP which only contains the unicast address of the source and multicast
> group
> (G) it represents. This register message does not contain data packet.____
>

There are implementations that only send null registers as well,
including for the initial register. Also, this is a unicast message.

> -  RP receives the register message and saves the information within the
> register
> message inside a table called Multicast Mapping Table (MMT). The RP puts
> an entry
> in MMT containing the unicast address of the source and the multicast
> group (G)
> it represents alongside other information related to the source for
> further use.
> -  After puting an entry in MMT RP will send back an acknowledge to the
> source
> which indicates the successful registration of the information sent by
> source.____

Which is a bit similar to responding with a register stop.
>
> -  after receiving the acknowledge from the RP source will start sending
> keep-alive
> messages to the RP as long as it represents the multicast traffic
> destined for (G).____

This is like the periodic PIM null registers.

> - in pim-sm a null register is in response to a register stop message
> sent by RP in case RP hasn’t received any join messages for the (G) a
> source is sending registers for. but since PIM-NG doesn't make use of
> RPT tree rooted at an RP and the RP doesn't need to receive a join
> message of (*,G)  to accept  a register message or join the RPT for
> (*,G) there will be only an acknowledge and a
> keep-alive.____

This part is different, I agree.
>
> -  the initial data packet does not need to be sent  because the overall
> process through which a last hop router (client) finds a source differs
> completely from that of PIM-SM.

Right, the data packet does not need to be sent for the multicast tree
to get constructed, but it means that applications will not get the
initial packet. There are other proposals with this shortcoming as well,
and for many applications this is fine. But at least this has a
significant impact on some applications, so it is worth emphasizing.
The different PIM protocols today usually allow for delivery of the
initial data packet. I should note that I'm proposing a way of
simplifying PIM-SM myself where initial packets would get dropped (by
avoiding PIM registers). So this is not unique to your proposal, and
I think it is OK for some deployments/applications.

> *2- How a last hop (a router which shows interest to receive multicast
> traffic
> destined for (G) or needs to find the source for (G) )learns about
> active sources? Source-discovery:*
>
> - in PIM-NG and in the ID, such a last hop router is called a client.____
>
>
> - In PIM-NG because of the way RP interacts with active sources and
> saves the
> information regarding active sources within the Domain in MMT, last hop
> (client)
> doesnt need to know about all the active sources within the Domain.____
>
>
> - considering the above, a client will contact the RP in case it needs
> to find the
> source of multicast traffic destined for (G) by sending a
> unicast-encapsulated
> request for source message to the RP indicating that it needs to find
> (S) for (G).
> ((there won't be a join to RPT for (*, G).))____
>
>
> - after RP receives the request it will search the MMT or
> AMMT(Abbreviated-MMT)
> to see if it finds an entry for (S) which represents (G).
>
> - If an entry is found in MMT or AMMT the RP will send a
> unicast-encapsulated
> acknowledge back to the client using the client's unicast address. This
> acknowledge
> contains the unicast address of the source for (G) along other
> information which is used by a client.____
>
>
> - If an entry is not found, a null acknowledge (*,G) will be sent back
> to the client.____
>
>
> - After receiving the acknowledge containing the unicast address of the
> source for
> (G) the client will directly join the SPT for (S, G).
> ((There will be no need for switching from RPT to SPT by the client
> (last hop).))
> - at this point a large number of clients or last hops won't be a
> problem due to the
> fact that there won't be any join to RPT rooted at the RP and the RP
> acts as an
> information station in PIM-NG which keeps the information regarding
> existing
> sources.____

This works well if the receiver is joining after the source started.
But what happens if the source starts later?

> -  A client (last hop) won't need to send periodical query messages for
> active source. A query is sent only when a client needs to find the
> source of a multicast traffic.

Assume that you have no active sources, but a host send an IGMP report
for a group G in order to receive. Then the client will send a request
to the RP as you described above, but it would not find any source
information.

Now if a source later starts to send, then you would like this host to
start receiving, but how does that happen? Either the client would need
to periodically query the RP, or the RP would need to keep track of
interested clients and send a notification.

Stig

> End of part 2.
>
>
>
> On Fri, Apr 25, 2014 at 10:32 PM, <pim-request@ietf.org
> <mailto:pim-request@ietf.org>> wrote:
>
>     Send pim mailing list submissions to
>     pim@ietf.org <mailto:pim@ietf.org>
>
>     To subscribe or unsubscribe via the World Wide Web, visit
>     https://www.ietf.org/mailman/listinfo/pim
>     or, via email, send a message with subject or body 'help' to
>     pim-request@ietf.org <mailto:pim-request@ietf.org>
>
>     You can reach the person managing the list at
>     pim-owner@ietf.org <mailto:pim-owner@ietf.org>
>
>     When replying, please edit your Subject line so it is more specific
>     than "Re: Contents of pim digest..."
>
>
>     Today's Topics:
>
>         1. Re: New updated and edited version of draft-sami-pim-ng
>            (Stig Venaas)
>         2. Re: New updated and edited version of draft-sami-pim-ng
>            (saeed sami)
>
>
>     ----------------------------------------------------------------------
>
>     Message: 1
>     Date: Thu, 24 Apr 2014 14:24:56 -0700
>     From: Stig Venaas <stig@venaas.com <mailto:stig@venaas.com>>
>     To: saeed sami <sami.biz.email@gmail.com
>     <mailto:sami.biz.email@gmail.com>>, pim <pim@ietf.org
>     <mailto:pim@ietf.org>>
>     Subject: Re: [pim] New updated and edited version of draft-sami-pim-ng
>     Message-ID: <53598128.1090107@venaas.com
>     <mailto:53598128.1090107@venaas.com>>
>     Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>     Hi
>
>     I have some comments on your draft. I've been hoping that others in the
>     working group would also comment on this. Maybe with my comments here we
>     can start a discussion and hopefully also get others in the working
>     group to take part.
>
>     On 4/10/2014 3:55 PM, saeed sami wrote:
>      > A new version of draft-sami-pim-ng is submitted and can be
>     reached at :
>      > http://www.ietf.org/internet-drafts/draft-sami-pim-ng-02.txt
>      >
>      > It is edited and some parts and sections are updated.
>      >
>      > Your reviews and comments are most appreciated. and I hope to
>     read the
>      > comments of PIM working group experts soon.
>      >
>      > Abstract:
>      >     This document specifies protocol independent multicast- Next
>      >     generation or simply called PIM-NG. like PIM-SM, PIM-NG uses the
>      >     underlying unicast routing information, but unlike PIM-SM it
>     doesn't
>      >     necessarily need to build unidirectional shared trees rooted at a
>      >     Rendezvous Point (RP) per group, due to the fact that the
>     processes
>      >     through which a source registers with the Rendezvous Point
>     and a host
>      >     finds the source of the multicast destination groups it needs are
>      >     done in a whole new way. So at some points PIM-NG works
>     faster than
>      >     its predecessor. Also the new Domain concept, unique to
>     PIM-NG, along
>      >     the RPF check method used in PIM-NG specifications provides many
>      >     features along a robust and flexible control and
>     administration over
>      >     multicast networks.
>
>     I see you have put a lot of work into this. There are a lot of concepts
>     defined, new message types etc. but I think the main difference from
>     PIM-SM that I want to focus on is the source discovery part (including
>     the behavior of RPs). I have not read about the domain concept in detail
>     yet. I think parts of what you are proposing could be achieved without
>     necessarily having a completely new PIM protocol.
>
>     Both in PIM-SM and in your proposal the RPs have knowledge of active
>     sources. How the RPs learn about the sources are not very different.
>
>     You propose a register message to be sent when the source becomes
>     active. It does not contain a data packet. With PIM-SM you could also
>     do this by sending a Null register. You also have periodic messages
>     for keeping this state alive, which is not really different from
>     sending periodic Null registers.
>
>     Your approach and the Null register approach work well except for one
>     issue. Initial data packets from a source would be dropped. This is a
>     concern for some applications. For many applications I think it is
>     acceptable though.
>
>     Now, what is very different in PIM-SM and your proposal is how the
>     last hop routers learn about active sources.
>
>     With your proposal my understanding is that a last hop router sends a
>     unicast query for sources to the RP to ask for active sources. Then you
>     have the last hop router send periodic queries every 30 seconds in case
>     there are new sources?
>
>     One issue I see here is scaling when there are a large number of last
>     hop routers. The more significant issue is I think that it may take up
>     to 30 seconds from a source starts sending until a last hop router
>     learns that the source is active. Is that correct? That is in my opinion
>     unacceptable for many applications. This could be improved if the RP
>     stores state, remembering that certain routers should be notified if a
>     new source becomes active. This could be a problem if there are a large
>     number of last hop routers though.
>
>     I can understand that it is nice to avoid data registers and shared
>     trees, but it has some impact on applications.
>
>     I would like to hear your thoughts on this. Both regarding my concerns
>     above, but also the advantages and issue you see with your approach
>     compared to PIM-SM.
>
>     I will be offline for the next 10 days, but hopefully this can get a
>     discussion started in the working group.
>
>     Stig
>
>
>
>
>
>
>
>
>
>
>
>     ------------------------------
>
> sincerely yours
> MR.SAEED SAMI
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>


From nobody Mon May 19 13:00:31 2014
Return-Path: <sami.biz.email@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66CF61A01DD for <pim@ietfa.amsl.com>; Mon, 19 May 2014 13:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.754
X-Spam-Level: 
X-Spam-Status: No, score=0.754 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, FRT_BELOW2=2.154, J_CHICKENPOX_41=0.6, SPF_PASS=-0.001] autolearn=no
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 tsh7zkysRuHA for <pim@ietfa.amsl.com>; Mon, 19 May 2014 13:00:26 -0700 (PDT)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 939321A0129 for <pim@ietf.org>; Mon, 19 May 2014 13:00:25 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id t60so6097728wes.13 for <pim@ietf.org>; Mon, 19 May 2014 13:00:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=5CValf4uniR5oyV7mz70wUIj1/1WMu3pW+R1klz8M/o=; b=FDm8HFokC7exU38P6l0IgP98OfSe3FlgsxUW9piXzJFPvdGe/KyieEfbx/SRQyWhZ4 J9UIhia7/PxiShDvp7iDGoHhAKb6euhoxfxx/byn1C26Ogm0mEcXsvVul+kfQYpzoBTV O/QpEziupQAyIOsnhMO6luPGwq4v2AO8KKMFZA7T4nKZp0YeJerGI42CUx8Gv/4jrHYg Jq02qx0r/GmkZa0ZiK06tsjpWyaJJmlzmXLaoCGccLEbXT68DhP0uKQjThUDWYfbGO6d EitBiTwno/LlgxM7m0P4Y/+8Wk2uiU9sgspDuSssb0H2yFNaughiW3gJtbzcWO1Ser9j 2AMA==
X-Received: by 10.180.13.113 with SMTP id g17mr457646wic.48.1400529624087; Mon, 19 May 2014 13:00:24 -0700 (PDT)
Received: from [192.168.1.3] ([178.253.58.65]) by mx.google.com with ESMTPSA id gi8sm16737698wib.8.2014.05.19.12.59.50 for <pim@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 19 May 2014 12:59:53 -0700 (PDT)
Message-ID: <537A6FCE.4080505@gmail.com>
Date: Tue, 20 May 2014 00:25:42 +0330
From: saeed sami <sami.biz.email@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: pim@ietf.org
References: <mailman.117.1400526038.17213.pim@ietf.org>
In-Reply-To: <mailman.117.1400526038.17213.pim@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/eOus3M-mmepW6EZ1DvCYb57rLQg
Subject: Re: [pim] New updated and edited version of draft-sami-pim-ng (part, 2)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 May 2014 20:00:30 -0000

Dear Mr.Venaas,
Hello.
First of all let me Thank you for your response and comments.
As i read your comments , i found out that there is one major question 
which is related to
a situation in which :
- the source becomes active after a client sends its query.
and secondly :
- the periodical query messages sent from clients to RP .


to make it more clear , let me explain the procedure and i think the 
issue will be resolved :

1- In PIM-NG a client will send query to RP in order to find the source 
of a multicast traffic (G), only
when it needs to receive the traffic destined for(G). the query is a 
unicast-encapsulated message.
2- if the source for (G) is already registered with the RP then the RP 
will find the (S) for (G) by looking
in its MMT or AMMT , and will return (S , G) back to the client by 
sending a unicast-encapsulated
acknowledge containing the unicast address of the source for (G).
3- after receiving the RP acknowledge containing the address of the 
source client will directly join the SPT for (S,G).

4- If the source is not registered yet( the case in question: source 
becomes active later), then the RP
will send back a null acknowledge message to the client.
5- After receiving the null acknowledge the client will start its timer 
and will query again in the next
T-second (default to 30).
6- client will continue sending its query messages until either it 
receives an acknowledge from RP
containing the unicast address of the source for (G) in the format of 
(S, G) or it doesnt need to
receive the multicast traffic destined for (G).

so in PIM-NG any query messages sent by clients , is generated and sent 
by the client only when it
needs to find the source of a multicast group (G). clients wont need to 
know about all the existing
or active sources.
I hope the above explanations are satisfactory.
thanks again and i hope taht other WG members will join the conversation 
soon enough.

sincerely
Saeed Sami
On 05/19/2014 10:30 Ø¨.Ø¸, pim-request@ietf.org wrote:
> Send pim mailing list submissions to
> 	pim@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/pim
> or, via email, send a message with subject or body 'help' to
> 	pim-request@ietf.org
>
> You can reach the person managing the list at
> 	pim-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pim digest..."
>
>
> Today's Topics:
>
>     1. Re: New updated and edited version of draft-sami-pim-ng (part
>        2) (Stig Venaas)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 19 May 2014 11:30:10 -0700
> From: Stig Venaas <stig@venaas.com>
> To: saeed sami <sami.biz.email@gmail.com>, pim <pim@ietf.org>
> Subject: Re: [pim] New updated and edited version of draft-sami-pim-ng
> 	(part	2)
> Message-ID: <537A4DB2.4040903@venaas.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> Hi
>
> Sorry for the late response, let me comment on this.
>
> On 4/29/2014 3:54 PM, saeed sami wrote:
>> Dear Mr.Venaas,
>> Hello
>> First of all let me thank you for your review, comments and the time you
>> have
>> dedicated to review my work "draft-sami-pim-ng-02".
>>
>> http://tools.ietf.org/html/draft-sami-pim-ng-02
>>
>> Since answering to your questions will be a little lengthy and cant be
>> posted to PIM mailing list as a single email, i have to post them in
>> separate  parts. and this is part 2.
>>
>> Please kindly find the answers and explanations to your questions and
>> doubts bellow. i hope that as you mentioned in your email there will be
>> more comments from other members after this.
>>
>> The answer to your questions are as follows which I hope will be
>> satisfying:
>>
>> *1- Source register process  in PIM-NG and its similarity to PIM-SM:*____
>>
>>
>> At the first glance the overall register process may seem similar to
>> PIM-SM, but
>> the register process in PIM-NG is different from PIM-SM. Bellow the
>> process is
>> briefly explained to make it clearer:____
>>
>>
>> -  Source sends a unicast-encapsulated register message to the address
>> of the
>> RP which only contains the unicast address of the source and multicast
>> group
>> (G) it represents. This register message does not contain data packet.____
>>
> There are implementations that only send null registers as well,
> including for the initial register. Also, this is a unicast message.
>
>> -  RP receives the register message and saves the information within the
>> register
>> message inside a table called Multicast Mapping Table (MMT). The RP puts
>> an entry
>> in MMT containing the unicast address of the source and the multicast
>> group (G)
>> it represents alongside other information related to the source for
>> further use.
>> -  After puting an entry in MMT RP will send back an acknowledge to the
>> source
>> which indicates the successful registration of the information sent by
>> source.____
> Which is a bit similar to responding with a register stop.
>> -  after receiving the acknowledge from the RP source will start sending
>> keep-alive
>> messages to the RP as long as it represents the multicast traffic
>> destined for (G).____
> This is like the periodic PIM null registers.
>
>> - in pim-sm a null register is in response to a register stop message
>> sent by RP in case RP hasn?t received any join messages for the (G) a
>> source is sending registers for. but since PIM-NG doesn't make use of
>> RPT tree rooted at an RP and the RP doesn't need to receive a join
>> message of (*,G)  to accept  a register message or join the RPT for
>> (*,G) there will be only an acknowledge and a
>> keep-alive.____
> This part is different, I agree.
>> -  the initial data packet does not need to be sent  because the overall
>> process through which a last hop router (client) finds a source differs
>> completely from that of PIM-SM.
> Right, the data packet does not need to be sent for the multicast tree
> to get constructed, but it means that applications will not get the
> initial packet. There are other proposals with this shortcoming as well,
> and for many applications this is fine. But at least this has a
> significant impact on some applications, so it is worth emphasizing.
> The different PIM protocols today usually allow for delivery of the
> initial data packet. I should note that I'm proposing a way of
> simplifying PIM-SM myself where initial packets would get dropped (by
> avoiding PIM registers). So this is not unique to your proposal, and
> I think it is OK for some deployments/applications.
>
>> *2- How a last hop (a router which shows interest to receive multicast
>> traffic
>> destined for (G) or needs to find the source for (G) )learns about
>> active sources? Source-discovery:*
>>
>> - in PIM-NG and in the ID, such a last hop router is called a client.____
>>
>>
>> - In PIM-NG because of the way RP interacts with active sources and
>> saves the
>> information regarding active sources within the Domain in MMT, last hop
>> (client)
>> doesnt need to know about all the active sources within the Domain.____
>>
>>
>> - considering the above, a client will contact the RP in case it needs
>> to find the
>> source of multicast traffic destined for (G) by sending a
>> unicast-encapsulated
>> request for source message to the RP indicating that it needs to find
>> (S) for (G).
>> ((there won't be a join to RPT for (*, G).))____
>>
>>
>> - after RP receives the request it will search the MMT or
>> AMMT(Abbreviated-MMT)
>> to see if it finds an entry for (S) which represents (G).
>>
>> - If an entry is found in MMT or AMMT the RP will send a
>> unicast-encapsulated
>> acknowledge back to the client using the client's unicast address. This
>> acknowledge
>> contains the unicast address of the source for (G) along other
>> information which is used by a client.____
>>
>>
>> - If an entry is not found, a null acknowledge (*,G) will be sent back
>> to the client.____
>>
>>
>> - After receiving the acknowledge containing the unicast address of the
>> source for
>> (G) the client will directly join the SPT for (S, G).
>> ((There will be no need for switching from RPT to SPT by the client
>> (last hop).))
>> - at this point a large number of clients or last hops won't be a
>> problem due to the
>> fact that there won't be any join to RPT rooted at the RP and the RP
>> acts as an
>> information station in PIM-NG which keeps the information regarding
>> existing
>> sources.____
> This works well if the receiver is joining after the source started.
> But what happens if the source starts later?
>
>> -  A client (last hop) won't need to send periodical query messages for
>> active source. A query is sent only when a client needs to find the
>> source of a multicast traffic.
> Assume that you have no active sources, but a host send an IGMP report
> for a group G in order to receive. Then the client will send a request
> to the RP as you described above, but it would not find any source
> information.
>
> Now if a source later starts to send, then you would like this host to
> start receiving, but how does that happen? Either the client would need
> to periodically query the RP, or the RP would need to keep track of
> interested clients and send a notification.
>
> Stig
>
>> End of part 2.
>>
>>
>>
>> On Fri, Apr 25, 2014 at 10:32 PM, <pim-request@ietf.org
>> <mailto:pim-request@ietf.org>> wrote:
>>
>>      Send pim mailing list submissions to
>>      pim@ietf.org <mailto:pim@ietf.org>
>>
>>      To subscribe or unsubscribe via the World Wide Web, visit
>>      https://www.ietf.org/mailman/listinfo/pim
>>      or, via email, send a message with subject or body 'help' to
>>      pim-request@ietf.org <mailto:pim-request@ietf.org>
>>
>>      You can reach the person managing the list at
>>      pim-owner@ietf.org <mailto:pim-owner@ietf.org>
>>
>>      When replying, please edit your Subject line so it is more specific
>>      than "Re: Contents of pim digest..."
>>
>>
>>      Today's Topics:
>>
>>          1. Re: New updated and edited version of draft-sami-pim-ng
>>             (Stig Venaas)
>>          2. Re: New updated and edited version of draft-sami-pim-ng
>>             (saeed sami)
>>
>>
>>      ----------------------------------------------------------------------
>>
>>      Message: 1
>>      Date: Thu, 24 Apr 2014 14:24:56 -0700
>>      From: Stig Venaas <stig@venaas.com <mailto:stig@venaas.com>>
>>      To: saeed sami <sami.biz.email@gmail.com
>>      <mailto:sami.biz.email@gmail.com>>, pim <pim@ietf.org
>>      <mailto:pim@ietf.org>>
>>      Subject: Re: [pim] New updated and edited version of draft-sami-pim-ng
>>      Message-ID: <53598128.1090107@venaas.com
>>      <mailto:53598128.1090107@venaas.com>>
>>      Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>>      Hi
>>
>>      I have some comments on your draft. I've been hoping that others in the
>>      working group would also comment on this. Maybe with my comments here we
>>      can start a discussion and hopefully also get others in the working
>>      group to take part.
>>
>>      On 4/10/2014 3:55 PM, saeed sami wrote:
>>       > A new version of draft-sami-pim-ng is submitted and can be
>>      reached at :
>>       > http://www.ietf.org/internet-drafts/draft-sami-pim-ng-02.txt
>>       >
>>       > It is edited and some parts and sections are updated.
>>       >
>>       > Your reviews and comments are most appreciated. and I hope to
>>      read the
>>       > comments of PIM working group experts soon.
>>       >
>>       > Abstract:
>>       >     This document specifies protocol independent multicast- Next
>>       >     generation or simply called PIM-NG. like PIM-SM, PIM-NG uses the
>>       >     underlying unicast routing information, but unlike PIM-SM it
>>      doesn't
>>       >     necessarily need to build unidirectional shared trees rooted at a
>>       >     Rendezvous Point (RP) per group, due to the fact that the
>>      processes
>>       >     through which a source registers with the Rendezvous Point
>>      and a host
>>       >     finds the source of the multicast destination groups it needs are
>>       >     done in a whole new way. So at some points PIM-NG works
>>      faster than
>>       >     its predecessor. Also the new Domain concept, unique to
>>      PIM-NG, along
>>       >     the RPF check method used in PIM-NG specifications provides many
>>       >     features along a robust and flexible control and
>>      administration over
>>       >     multicast networks.
>>
>>      I see you have put a lot of work into this. There are a lot of concepts
>>      defined, new message types etc. but I think the main difference from
>>      PIM-SM that I want to focus on is the source discovery part (including
>>      the behavior of RPs). I have not read about the domain concept in detail
>>      yet. I think parts of what you are proposing could be achieved without
>>      necessarily having a completely new PIM protocol.
>>
>>      Both in PIM-SM and in your proposal the RPs have knowledge of active
>>      sources. How the RPs learn about the sources are not very different.
>>
>>      You propose a register message to be sent when the source becomes
>>      active. It does not contain a data packet. With PIM-SM you could also
>>      do this by sending a Null register. You also have periodic messages
>>      for keeping this state alive, which is not really different from
>>      sending periodic Null registers.
>>
>>      Your approach and the Null register approach work well except for one
>>      issue. Initial data packets from a source would be dropped. This is a
>>      concern for some applications. For many applications I think it is
>>      acceptable though.
>>
>>      Now, what is very different in PIM-SM and your proposal is how the
>>      last hop routers learn about active sources.
>>
>>      With your proposal my understanding is that a last hop router sends a
>>      unicast query for sources to the RP to ask for active sources. Then you
>>      have the last hop router send periodic queries every 30 seconds in case
>>      there are new sources?
>>
>>      One issue I see here is scaling when there are a large number of last
>>      hop routers. The more significant issue is I think that it may take up
>>      to 30 seconds from a source starts sending until a last hop router
>>      learns that the source is active. Is that correct? That is in my opinion
>>      unacceptable for many applications. This could be improved if the RP
>>      stores state, remembering that certain routers should be notified if a
>>      new source becomes active. This could be a problem if there are a large
>>      number of last hop routers though.
>>
>>      I can understand that it is nice to avoid data registers and shared
>>      trees, but it has some impact on applications.
>>
>>      I would like to hear your thoughts on this. Both regarding my concerns
>>      above, but also the advantages and issue you see with your approach
>>      compared to PIM-SM.
>>
>>      I will be offline for the next 10 days, but hopefully this can get a
>>      discussion started in the working group.
>>
>>      Stig
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>      ------------------------------
>>
>> sincerely yours
>> MR.SAEED SAMI
>>
>>
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim
>>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>
>
> ------------------------------
>
> End of pim Digest, Vol 121, Issue 2
> ***********************************


From nobody Mon May 19 16:09:40 2014
Return-Path: <jasghar@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB881A042F for <pim@ietfa.amsl.com>; Mon, 19 May 2014 16:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 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, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 JY2UleUySR6K for <pim@ietfa.amsl.com>; Mon, 19 May 2014 16:09:36 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C07A1A0422 for <pim@ietf.org>; Mon, 19 May 2014 16:09:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=34893; q=dns/txt; s=iport; t=1400540976; x=1401750576; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=sl8GbRNPDY1XFhFLqSfEgvRMLA+2GtcsylvWmXs4sIc=; b=AfkUmBIJl+Z66ySGcO1/BMov3JbpQgEhvAaLCaZLFhc9bFB1iUpU84oX Nd2ktzkHuTk2HqbS+/bChoFWtJ4onwaGZdAo1Jhgch9cHVMjHn6Oc07GC npbEYXXla7FLfgFeYYcYpwzPzkyGl8qe+wt6oSw5TNbJyg7jJ10Wb6Kyz k=;
X-IronPort-AV: E=Sophos; i="4.98,870,1392163200"; d="scan'208,217"; a="45279894"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-1.cisco.com with ESMTP; 19 May 2014 23:09:35 +0000
Received: from [10.21.92.173] (sjc-vpn5-1197.cisco.com [10.21.92.173]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s4JN9SNX032302; Mon, 19 May 2014 23:09:28 GMT
Message-ID: <537A8F27.40205@cisco.com>
Date: Tue, 20 May 2014 01:09:27 +0200
From: Javed Asghar <jasghar@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>, IJsbrand Wijnands <ice@cisco.com>
References: <008e01cf1a88$eefd3600$ccf7a200$@olddog.co.uk>	<533BC9AE.8020602@cisco.com>	<061601cf4e9b$adb85570$09290050$@olddog.co.uk>	<85DAD28B-6A14-4BEB-B324-816A0FFA347D@cisco.com> <CAG4d1rebTqG3Y7b8iDMTRSZJoCzyhomuCi4poAcohsPsc_Za3w@mail.gmail.com>
In-Reply-To: <CAG4d1rebTqG3Y7b8iDMTRSZJoCzyhomuCi4poAcohsPsc_Za3w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040103030606020903040407"
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/w7DxFokp_LqtD4ddw8Ar9avuLSo
Cc: draft-ietf-pim-explicit-rpf-vector.all@tools.ietf.org, Alia Atlas <akatlas@juniper.net>, pim@ietf.org
Subject: Re: [pim] AD review of draft-ietf-pim-explicit-rpf-vector
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 May 2014 23:09:39 -0000

This is a multi-part message in MIME format.
--------------040103030606020903040407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Alia,

Did you get a chance to review? Its been awhile.
If its ok, we'd like to move it forward.

Thanks,
-Javed.

On 4/3/2014 3:11 PM, Alia Atlas wrote:
> Thanks for updating the draft.  I will review it very soon so we can 
> get it moving along.
>
> Alia
>
>
> On Thu, Apr 3, 2014 at 9:07 AM, IJsbrand Wijnands <ice@cisco.com 
> <mailto:ice@cisco.com>> wrote:
>
>     Thanks Adrian,
>
>     > Forwarded to Alia who now has the joy of being your AD.
>     >
>     > From me, just to note that you cannot demand a code point from
>     IANA, you can only request one. The way to do it is to use the TBD
>     form of the text I suggested and then say. "It is requested that
>     IANA assign the value 4."
>
>     We'll change it to say 'requested'.
>
>     >
>     > Note for future reference that if you feel an attachment for a
>     specific code point you really, really need to apply for an early
>     allocation (RFC 7120) because someone else might come along in the
>     intervening time and use your value for something else.
>
>     Yes, we know about that. I remember discussing it with Stig at one
>     point, but since this was the only draft in the queue to request
>     such value I think the conclusion was that its not necessary to do
>     early allocation, but your right, we should really always do that
>     to be safe.
>
>     Thx,
>
>     Ice.
>
>
>     >
>     > Adrian
>     >
>     > From: Javed Asghar [mailto:jasghar@cisco.com
>     <mailto:jasghar@cisco.com>]
>     > Sent: 02 April 2014 09:26
>     > To: adrian@olddog.co.uk <mailto:adrian@olddog.co.uk>;
>     draft-ietf-pim-explicit-rpf-vector
>     > Subject: Re: AD review of draft-ietf-pim-explicit-rpf-vector
>     >
>     > Hi,
>     >
>     > Submitted updated draft:
>     http://www.ietf.org/internet-drafts/draft-ietf-pim-explicit-rpf-vector-04.txt
>     > Please see comments inline below.
>     >
>     > Cheers,
>     > -Javed.
>     >
>     >
>     > On 1/26/2014 3:22 AM, Adrian Farrel wrote:
>     > Hi,
>     >
>     > I have done my usual AD review of this document after receiving the
>     > publication request. The purpose of the review is to catch and fix
>     > any issues that might otherwise show up in IETF last call or IESG
>     > review. This helps smooth the passage of the document later and also
>     > increases the quality text.
>     >
>     > This seems like a good and simple proposal, and I don't want to bog
>     > it down. But there are a number of small editorial issues and a
>     > couple of technical questions included below.
>     >
>     > I have put the document into "Revised I-D Needed" state and will
>     > wait to see an updated version before I start the IETF last call.
>     > But please feel free to debate any of these points with me.
>     >
>     > Thanks for the work.
>     >
>     > Adrian
>     >
>     > ---
>     >
>     > You need to fix the idnits before I can put this to IETF last call.
>     >
>     > - Missing page breaks
>     > - 2119 boilerplate broken (you have "SHALL" "NOT")
>     > - there is a line too long
>     > - missing reference for [draft-mofrr-karan]
>     >
>     > [Shepherd - Your write-up says no nits found. How come?]
>     >
>     > ---
>     >
>     > Conventionally we have used the term "strict" in counterpoint to
>     > "loose" to describe hops, and termed the whole path "explicit". I
>     > don't suppose this matters: you are defining your own terms for a
>     > new application in PIM.
>     >
>     > However, this has led to some confusion in the text because of the
>     > normal use of the English word "explicit". For example, the Abstract
>     > says:
>     >    This document defines a new Reverse Path Forwarding (RPF) Vector
>     >    TLV to build multicast trees via an explicit path sent in the PIM
>     >    join.
>     > ...which doesn't give any clue to the distinction between this work
>     > and RFC 5496. You might be better with something like:
>     >    The PIM Reverse Path Forwarding (RPF) Vector TLV defined in
>     RFC 5496
>     >    can be included in a PIM Join Attribute to allow a leaf to apply
>     >    controls to the path of a multicast tree. This document defines a
>     >    new Vector Attribute type so that an RPF Vector TLV can be
>     used to
>     >    indicate that the unicast address indicated in the TLV must
>     be used
>     >    as the next hop in the multicast tree.
>     >
>     > This kind of language could usefully be repeated throughout the
>     > document.
>     >
>     > JA>>> Updated
>     >
>     >
>     > ---
>     >
>     > Section 1
>     >
>     >    For some applications, it might be useful to have a way to
>     specify
>     >    the explicit path along which the PIM join is propagated.
>     >
>     > Could you possibly be a little less vague? :-)
>     > If this is the level of certainty you have for the utility of
>     your work
>     > then it shouldn't be on the Standards Track. Fortunately, you
>     *do* have
>     > a good use case later in the document.
>     >
>     > I suggest re-ordering paragraphs:
>     >
>     > 3, 4, 2
>     >
>     > ...and delete paragraph 1.
>     >
>     > ---
>     >
>     > JA>>> Updated.
>     >
>     >
>     > Suggest to rename Section 3 "Motivation"
>     >
>     > ---
>     >
>     > JA>>> Updated
>     >
>     >
>     > Section 3
>     >
>     > As noted above, you need to provide the reference for
>     > [draft-mofrr-karan]. But actually, I wonder whether you really
>     need to
>     > include the citation as the text in the paragraph seems to hold
>     up well
>     > without any further explanation.
>     >
>     > ---
>     >
>     > JA>>> Updated.
>     >
>     >
>     > Section 3
>     >
>     >    It might be useful to have a way to specify the explicit path
>     >    along which the PIM join is propagated.
>     >
>     > I think you established that it *is* useful in the previous text.
>     >
>     > JA>>> Corrected.
>     >
>     >
>     > ---
>     >
>     > Section 3
>     >
>     >    How the Explicit RPF Vector list is determined is outside the
>     >    scope of this document. It may either be manually configured by
>     >    the network operator or procedures may be implemented on the
>     >    egress router to dynamically calculate the vector list based on
>     >    a link state database protocol, like OSPF or IS-IS.
>     >
>     > I agree that this should be out of scope and you should say so.
>     > However, having said it is out of scope, why do you go on to
>     > discuss it?
>     >
>     > JA>>> Ack. This is implementation specific. We have changed this
>     discussion as example. This was feedback from previous reviews.
>     >
>     >
>     > ---
>     >
>     > You should give more clarity as to why an RPF list using 5496 list
>     > entries would not be good enough. In Figure 1 it would appear
>     that the
>     > list {R4, R3, R6, R5, R2, R1} would work just fine using 5496.
>     >
>     > JA>>> Added more clarity with a comparison between Explicit RPF
>     Vector and RFC5496 procedures.
>     >
>     >
>     > ---
>     >
>     > Section 5
>     >
>     >    This draft uses PIM join attribute type 4 for specifying an
>     Explicit
>     >    RPF Vector.
>     >
>     > Please make this:
>     >
>     >    This draft uses PIM join attribute type TBD by IANA for
>     specifying an
>     >    Explicit RPF Vector.
>     >
>     > ---
>     >
>     > JA>>> Updated.
>     >
>     >
>     > Section 7 is describing, for example, simple network with source
>     S and
>     > leafs R1 and R2...
>     >
>     >   A   R1
>     >  / \ /
>     > S   C
>     >  \ / \
>     >   B   R2
>     >
>     > ...where R1 sends explicit RPF TLVs {C, A} and that path is set up.
>     > Then R2 sends explicit RPF TLVs {C, B}.
>     >
>     > Section 3.3.3 of RFC 5384 is cited as the tie-breaker.
>     > This is OK, but it appears to say that the Explicit RPF is not
>     > mandatory. It would be nice to make it very clear that a
>     receiver has
>     > no expectations that the explicit RPF list it supplies will
>     actually be
>     > used.
>     >
>     > JA>>> There is no change in our draft with respect to this
>     behavior and its documented well in RFC 5384 section 3.3.3. Adding
>     more text could confuse the reader. We felt the current text is
>     sufficient. Let us know if this is ok with you.
>     >
>     >
>     > ---
>     >
>     > Section 10
>     >
>     > This is important material to include, but I think it needs some
>     work.
>     >
>     >    The F bit MUST be set to 0 by a downstream router in the join
>     that
>     >    is sent to the upstream router that does not support Explicit RPF
>     >    vector.
>     >
>     > But the downstream router doesn't know whether the upstream router
>     > supports the new vector or not! So I think you need...
>     >
>     >    The F bit MUST be set to 0 in all Explicit RPF vectors in
>     case the
>     >    upstream router receiving the join does not support the TLV. As
>     >    described in section 3.3.2 of [RFC5384], routers that do not
>     >    understand the type of a particular attribute that has the F bit
>     >    clear will discard it and continue to process the join.
>     >
>     >    This processing is particularly important when the routers that
>     >    do not support the Explicit RPF TLV are identified as hops in the
>     >    explicit RPF list, because failing to remove the RPF vectors
>     could
>     >    cause upstream routers to send the join back toward these routers
>     >    causing loops.
>     >
>     > JA>>> Updated. Thanks for the clarity. Its very precise.
>     >
>     >
>     >
>     > However, this doesn't seem to be the only way that loops can be
>     caused
>     > (referring back to section 9).
>     > I don't see this mentioned in RFC 5496 either, but surely:
>     > - the RPF list could contain an explicit loop
>     > - the use of loose hops with poorly ordered list entries could
>     create a
>     >   loop
>     >
>     > It is fine to note that this is caught by normal PIM processing, but
>     > you should say so, and you should say what happens to the join. It
>     > seems to me that 3.3.4 of 5496 only catches the case where join is
>     > targeting the same upstream neighbor. But the sequential list nature
>     > of the RPF list means that the loop might not be "endless" but could
>     > still be a loop. How is this caught and handled?
>     >
>     >
>     > JA>>> Please note that the explicit or loose RPF vector list at
>     every hop will consume the RPF vector entry. If an explicit or
>     loose RPF vector list is constructed poorly (eg. mis-config) the
>     processing of the RPF vector is still as described in RFC 5496 and
>     doesn't need to change. We need to fix the user error.
>     >
>     >
>     > ---
>     >
>     > Section 11
>     >
>     > Please replace...
>     >
>     > OLD
>     >    Type
>     >    ----
>     >    The Vector Attribute type is 4.
>     > NEW
>     >    Type
>     >    ----
>     >    The Vector Attribute type is TBD by IANA.
>     > END
>     >
>     > ---
>     >
>     > JA>>> We would like to request type 4 attribute from IANA
>     explicitly.
>     >
>     >
>     > Section 13 seems light!
>     >
>     > The RPF list (and especially the explicit RPF) provides a way to
>     > cause traffic to take different routes through the network. This
>     > could be used to cause traffic to take expensive paths, to be
>     > routed through hot parts of the network, or to be directed to
>     > snooping nodes.
>     >
>     > This means that the existence of the RPF TLV makes the use of
>     > security in PIM more important to prevent tampering with the RPF
>     > list.
>     > JA>>> Good point.
>     >
>     >
>     > But it also raises a question of policy and authorization. Clearly,
>     > when a receiver seeks to join a multicast tree, it must be
>     > authenticated for that join. But additionally, you may want to note
>     > that the inclusion of an RPF list by a receiver should be subject to
>     > policy.
>     >
>     > JA>>> Updated.
>     >
>     >
>     > .
>     >
>     >
>
>     _______________________________________________
>     pim mailing list
>     pim@ietf.org <mailto:pim@ietf.org>
>     https://www.ietf.org/mailman/listinfo/pim
>
>


--------------040103030606020903040407
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Alia, <br>
    <br>
    Did you get a chance to review? Its been awhile. <br>
    If its ok, we'd like to move it forward. <br>
    <br>
    Thanks,<br>
    -Javed.<br>
    <br>
    <div class="moz-cite-prefix">On 4/3/2014 3:11 PM, Alia Atlas wrote:<br>
    </div>
    <blockquote
cite="mid:CAG4d1rebTqG3Y7b8iDMTRSZJoCzyhomuCi4poAcohsPsc_Za3w@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr">Thanks for updating the draft. &nbsp;I will review it
        very soon so we can get it moving along.
        <div><br>
        </div>
        <div>Alia</div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Thu, Apr 3, 2014 at 9:07 AM,
          IJsbrand Wijnands <span dir="ltr">&lt;<a
              moz-do-not-send="true" href="mailto:ice@cisco.com"
              target="_blank">ice@cisco.com</a>&gt;</span> wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks
            Adrian,<br>
            <div class=""><br>
              &gt; Forwarded to Alia who now has the joy of being your
              AD.<br>
              &gt;<br>
              &gt; From me, just to note that you cannot demand a code
              point from IANA, you can only request one. The way to do
              it is to use the TBD form of the text I suggested and then
              say. "It is requested that IANA assign the value 4."<br>
              <br>
            </div>
            We'll change it to say 'requested'.<br>
            <div class=""><br>
              &gt;<br>
              &gt; Note for future reference that if you feel an
              attachment for a specific code point you really, really
              need to apply for an early allocation (RFC 7120) because
              someone else might come along in the intervening time and
              use your value for something else.<br>
              <br>
            </div>
            Yes, we know about that. I remember discussing it with Stig
            at one point, but since this was the only draft in the queue
            to request such value I think the conclusion was that its
            not necessary to do early allocation, but your right, we
            should really always do that to be safe.<br>
            <br>
            Thx,<br>
            <br>
            Ice.<br>
            <div>
              <div class="h5"><br>
                <br>
                &gt;<br>
                &gt; Adrian<br>
                &gt;<br>
                &gt; From: Javed Asghar [mailto:<a
                  moz-do-not-send="true" href="mailto:jasghar@cisco.com">jasghar@cisco.com</a>]<br>
                &gt; Sent: 02 April 2014 09:26<br>
                &gt; To: <a moz-do-not-send="true"
                  href="mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>;
                draft-ietf-pim-explicit-rpf-vector<br>
                &gt; Subject: Re: AD review of
                draft-ietf-pim-explicit-rpf-vector<br>
                &gt;<br>
                &gt; Hi,<br>
                &gt;<br>
                &gt; Submitted updated draft: <a moz-do-not-send="true"
href="http://www.ietf.org/internet-drafts/draft-ietf-pim-explicit-rpf-vector-04.txt"
                  target="_blank">http://www.ietf.org/internet-drafts/draft-ietf-pim-explicit-rpf-vector-04.txt</a><br>
                &gt; Please see comments inline below.<br>
                &gt;<br>
                &gt; Cheers,<br>
                &gt; -Javed.<br>
                &gt;<br>
                &gt;<br>
                &gt; On 1/26/2014 3:22 AM, Adrian Farrel wrote:<br>
                &gt; Hi,<br>
                &gt;<br>
                &gt; I have done my usual AD review of this document
                after receiving the<br>
                &gt; publication request. The purpose of the review is
                to catch and fix<br>
                &gt; any issues that might otherwise show up in IETF
                last call or IESG<br>
                &gt; review. This helps smooth the passage of the
                document later and also<br>
                &gt; increases the quality text.<br>
                &gt;<br>
                &gt; This seems like a good and simple proposal, and I
                don't want to bog<br>
                &gt; it down. But there are a number of small editorial
                issues and a<br>
                &gt; couple of technical questions included below.<br>
                &gt;<br>
                &gt; I have put the document into "Revised I-D Needed"
                state and will<br>
                &gt; wait to see an updated version before I start the
                IETF last call.<br>
                &gt; But please feel free to debate any of these points
                with me.<br>
                &gt;<br>
                &gt; Thanks for the work.<br>
                &gt;<br>
                &gt; Adrian<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; You need to fix the idnits before I can put this to
                IETF last call.<br>
                &gt;<br>
                &gt; - Missing page breaks<br>
                &gt; - 2119 boilerplate broken (you have "SHALL" "NOT")<br>
                &gt; - there is a line too long<br>
                &gt; - missing reference for [draft-mofrr-karan]<br>
                &gt;<br>
                &gt; [Shepherd - Your write-up says no nits found. How
                come?]<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; Conventionally we have used the term "strict" in
                counterpoint to<br>
                &gt; "loose" to describe hops, and termed the whole path
                "explicit". I<br>
                &gt; don't suppose this matters: you are defining your
                own terms for a<br>
                &gt; new application in PIM.<br>
                &gt;<br>
                &gt; However, this has led to some confusion in the text
                because of the<br>
                &gt; normal use of the English word "explicit". For
                example, the Abstract<br>
                &gt; says:<br>
                &gt; &nbsp; &nbsp;This document defines a new Reverse Path
                Forwarding (RPF) Vector<br>
                &gt; &nbsp; &nbsp;TLV to build multicast trees via an explicit
                path sent in the PIM<br>
                &gt; &nbsp; &nbsp;join.<br>
                &gt; ...which doesn't give any clue to the distinction
                between this work<br>
                &gt; and RFC 5496. You might be better with something
                like:<br>
                &gt; &nbsp; &nbsp;The PIM Reverse Path Forwarding (RPF) Vector TLV
                defined in RFC 5496<br>
                &gt; &nbsp; &nbsp;can be included in a PIM Join Attribute to allow
                a leaf to apply<br>
                &gt; &nbsp; &nbsp;controls to the path of a multicast tree. This
                document defines a<br>
                &gt; &nbsp; &nbsp;new Vector Attribute type so that an RPF Vector
                TLV can be used to<br>
                &gt; &nbsp; &nbsp;indicate that the unicast address indicated in
                the TLV must be used<br>
                &gt; &nbsp; &nbsp;as the next hop in the multicast tree.<br>
                &gt;<br>
                &gt; This kind of language could usefully be repeated
                throughout the<br>
                &gt; document.<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Updated<br>
                &gt;<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; Section 1<br>
                &gt;<br>
                &gt; &nbsp; &nbsp;For some applications, it might be useful to
                have a way to specify<br>
                &gt; &nbsp; &nbsp;the explicit path along which the PIM join is
                propagated.<br>
                &gt;<br>
                &gt; Could you possibly be a little less vague? :-)<br>
                &gt; If this is the level of certainty you have for the
                utility of your work<br>
                &gt; then it shouldn't be on the Standards Track.
                Fortunately, you *do* have<br>
                &gt; a good use case later in the document.<br>
                &gt;<br>
                &gt; I suggest re-ordering paragraphs:<br>
                &gt;<br>
                &gt; 3, 4, 2<br>
                &gt;<br>
                &gt; ...and delete paragraph 1.<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Updated.<br>
                &gt;<br>
                &gt;<br>
                &gt; Suggest to rename Section 3 "Motivation"<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Updated<br>
                &gt;<br>
                &gt;<br>
                &gt; Section 3<br>
                &gt;<br>
                &gt; As noted above, you need to provide the reference
                for<br>
                &gt; [draft-mofrr-karan]. But actually, I wonder whether
                you really need to<br>
                &gt; include the citation as the text in the paragraph
                seems to hold up well<br>
                &gt; without any further explanation.<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Updated.<br>
                &gt;<br>
                &gt;<br>
                &gt; Section 3<br>
                &gt;<br>
                &gt; &nbsp; &nbsp;It might be useful to have a way to specify the
                explicit path<br>
                &gt; &nbsp; &nbsp;along which the PIM join is propagated.<br>
                &gt;<br>
                &gt; I think you established that it *is* useful in the
                previous text.<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Corrected.<br>
                &gt;<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; Section 3<br>
                &gt;<br>
                &gt; &nbsp; &nbsp;How the Explicit RPF Vector list is determined
                is outside the<br>
                &gt; &nbsp; &nbsp;scope of this document. It may either be
                manually configured by<br>
                &gt; &nbsp; &nbsp;the network operator or procedures may be
                implemented on the<br>
                &gt; &nbsp; &nbsp;egress router to dynamically calculate the
                vector list based on<br>
                &gt; &nbsp; &nbsp;a link state database protocol, like OSPF or
                IS-IS.<br>
                &gt;<br>
                &gt; I agree that this should be out of scope and you
                should say so.<br>
                &gt; However, having said it is out of scope, why do you
                go on to<br>
                &gt; discuss it?<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Ack. This is implementation
                specific. We have changed this discussion as example.
                This was feedback from previous reviews.<br>
                &gt;<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; You should give more clarity as to why an RPF list
                using 5496 list<br>
                &gt; entries would not be good enough. In Figure 1 it
                would appear that the<br>
                &gt; list {R4, R3, R6, R5, R2, R1} would work just fine
                using 5496.<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Added more clarity with a comparison
                between Explicit RPF Vector and RFC5496 procedures.<br>
                &gt;<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; Section 5<br>
                &gt;<br>
                &gt; &nbsp; &nbsp;This draft uses PIM join attribute type 4 for
                specifying an Explicit<br>
                &gt; &nbsp; &nbsp;RPF Vector.<br>
                &gt;<br>
                &gt; Please make this:<br>
                &gt;<br>
                &gt; &nbsp; &nbsp;This draft uses PIM join attribute type TBD by
                IANA for specifying an<br>
                &gt; &nbsp; &nbsp;Explicit RPF Vector.<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Updated.<br>
                &gt;<br>
                &gt;<br>
                &gt; Section 7 is describing, for example, simple
                network with source S and<br>
                &gt; leafs R1 and R2...<br>
                &gt;<br>
                &gt; &nbsp; A &nbsp; R1<br>
                &gt; &nbsp;/ \ /<br>
                &gt; S &nbsp; C<br>
                &gt; &nbsp;\ / \<br>
                &gt; &nbsp; B &nbsp; R2<br>
                &gt;<br>
                &gt; ...where R1 sends explicit RPF TLVs {C, A} and that
                path is set up.<br>
                &gt; Then R2 sends explicit RPF TLVs {C, B}.<br>
                &gt;<br>
                &gt; Section 3.3.3 of RFC 5384 is cited as the
                tie-breaker.<br>
                &gt; This is OK, but it appears to say that the Explicit
                RPF is not<br>
                &gt; mandatory. It would be nice to make it very clear
                that a receiver has<br>
                &gt; no expectations that the explicit RPF list it
                supplies will actually be<br>
                &gt; used.<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; There is no change in our draft with
                respect to this behavior and its documented well in RFC
                5384 section 3.3.3. Adding more text could confuse the
                reader. We felt the current text is sufficient. Let us
                know if this is ok with you.<br>
                &gt;<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; Section 10<br>
                &gt;<br>
                &gt; This is important material to include, but I think
                it needs some work.<br>
                &gt;<br>
                &gt; &nbsp; &nbsp;The F bit MUST be set to 0 by a downstream
                router in the join that<br>
                &gt; &nbsp; &nbsp;is sent to the upstream router that does not
                support Explicit RPF<br>
                &gt; &nbsp; &nbsp;vector.<br>
                &gt;<br>
                &gt; But the downstream router doesn't know whether the
                upstream router<br>
                &gt; supports the new vector or not! So I think you
                need...<br>
                &gt;<br>
                &gt; &nbsp; &nbsp;The F bit MUST be set to 0 in all Explicit RPF
                vectors in case the<br>
                &gt; &nbsp; &nbsp;upstream router receiving the join does not
                support the TLV. As<br>
                &gt; &nbsp; &nbsp;described in section 3.3.2 of [RFC5384], routers
                that do not<br>
                &gt; &nbsp; &nbsp;understand the type of a particular attribute
                that has the F bit<br>
                &gt; &nbsp; &nbsp;clear will discard it and continue to process
                the join.<br>
                &gt;<br>
                &gt; &nbsp; &nbsp;This processing is particularly important when
                the routers that<br>
                &gt; &nbsp; &nbsp;do not support the Explicit RPF TLV are
                identified as hops in the<br>
                &gt; &nbsp; &nbsp;explicit RPF list, because failing to remove the
                RPF vectors could<br>
                &gt; &nbsp; &nbsp;cause upstream routers to send the join back
                toward these routers<br>
                &gt; &nbsp; &nbsp;causing loops.<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Updated. Thanks for the clarity. Its
                very precise.<br>
                &gt;<br>
                &gt;<br>
                &gt;<br>
                &gt; However, this doesn't seem to be the only way that
                loops can be caused<br>
                &gt; (referring back to section 9).<br>
                &gt; I don't see this mentioned in RFC 5496 either, but
                surely:<br>
                &gt; - the RPF list could contain an explicit loop<br>
                &gt; - the use of loose hops with poorly ordered list
                entries could create a<br>
                &gt; &nbsp; loop<br>
                &gt;<br>
                &gt; It is fine to note that this is caught by normal
                PIM processing, but<br>
                &gt; you should say so, and you should say what happens
                to the join. It<br>
                &gt; seems to me that 3.3.4 of 5496 only catches the
                case where join is<br>
                &gt; targeting the same upstream neighbor. But the
                sequential list nature<br>
                &gt; of the RPF list means that the loop might not be
                "endless" but could<br>
                &gt; still be a loop. How is this caught and handled?<br>
                &gt;<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Please note that the explicit or
                loose RPF vector list at every hop will consume the RPF
                vector entry. If an explicit or loose RPF vector list is
                constructed poorly (eg. mis-config) the processing of
                the RPF vector is still as described in RFC 5496 and
                doesn't need to change. We need to fix the user error.<br>
                &gt;<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; Section 11<br>
                &gt;<br>
                &gt; Please replace...<br>
                &gt;<br>
                &gt; OLD<br>
                &gt; &nbsp; &nbsp;Type<br>
                &gt; &nbsp; &nbsp;----<br>
                &gt; &nbsp; &nbsp;The Vector Attribute type is 4.<br>
                &gt; NEW<br>
                &gt; &nbsp; &nbsp;Type<br>
                &gt; &nbsp; &nbsp;----<br>
                &gt; &nbsp; &nbsp;The Vector Attribute type is TBD by IANA.<br>
                &gt; END<br>
                &gt;<br>
                &gt; ---<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; We would like to request type 4
                attribute from IANA explicitly.<br>
                &gt;<br>
                &gt;<br>
                &gt; Section 13 seems light!<br>
                &gt;<br>
                &gt; The RPF list (and especially the explicit RPF)
                provides a way to<br>
                &gt; cause traffic to take different routes through the
                network. This<br>
                &gt; could be used to cause traffic to take expensive
                paths, to be<br>
                &gt; routed through hot parts of the network, or to be
                directed to<br>
                &gt; snooping nodes.<br>
                &gt;<br>
                &gt; This means that the existence of the RPF TLV makes
                the use of<br>
                &gt; security in PIM more important to prevent tampering
                with the RPF<br>
                &gt; list.<br>
                &gt; JA&gt;&gt;&gt; Good point.<br>
                &gt;<br>
                &gt;<br>
                &gt; But it also raises a question of policy and
                authorization. Clearly,<br>
                &gt; when a receiver seeks to join a multicast tree, it
                must be<br>
                &gt; authenticated for that join. But additionally, you
                may want to note<br>
                &gt; that the inclusion of an RPF list by a receiver
                should be subject to<br>
                &gt; policy.<br>
                &gt;<br>
                &gt; JA&gt;&gt;&gt; Updated.<br>
                &gt;<br>
                &gt;<br>
                &gt; .<br>
                &gt;<br>
                &gt;<br>
                <br>
              </div>
            </div>
            _______________________________________________<br>
            pim mailing list<br>
            <a moz-do-not-send="true" href="mailto:pim@ietf.org">pim@ietf.org</a><br>
            <a moz-do-not-send="true"
              href="https://www.ietf.org/mailman/listinfo/pim"
              target="_blank">https://www.ietf.org/mailman/listinfo/pim</a><br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------040103030606020903040407--


From nobody Tue May 20 12:07:03 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1BFB1A0755 for <pim@ietfa.amsl.com>; Tue, 20 May 2014 12:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 y29QgPb1BcaB for <pim@ietfa.amsl.com>; Tue, 20 May 2014 12:06:59 -0700 (PDT)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 296B11A077F for <pim@ietf.org>; Tue, 20 May 2014 12:06:59 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id b6so763041yha.32 for <pim@ietf.org>; Tue, 20 May 2014 12:06:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wxBmZKB4rRqVZHN1WpV8AwH7hou3tozv34cMrB2mFEg=; b=T0mk3SEzpYpdlnDhvIoURX4v0l0/SVjCq9QnzkV2hfNUMmmtO7X7PLiLecmZc85u+e QaKZLtK9V4disP2IqRCHBjbFLVS1EASPL5WV+dKNgKf0md7s23U44xKZiI/s41hHZrqx QNYU5Mvgkz1m8oMup1UOCqIkxlLg6oxgC4rLD9ZgbCqYVxTNoAtdRYZmhQ/aK1Gtf2dn rmejtBe74bWabjFWDNZqbZLQT1EcKZ4HE6Pj6EKlMk3a8WfVJHqitI33pQuK9uTKH2V6 Wnr+q0rzuFcgr00JCmlw5arqpg/JyvlVY9lj4e2dMh0Avu6OqeMOKLPy5bWpEygzXIgw veVw==
MIME-Version: 1.0
X-Received: by 10.236.168.42 with SMTP id j30mr66465733yhl.101.1400612818258;  Tue, 20 May 2014 12:06:58 -0700 (PDT)
Received: by 10.170.194.2 with HTTP; Tue, 20 May 2014 12:06:58 -0700 (PDT)
In-Reply-To: <537A8F27.40205@cisco.com>
References: <008e01cf1a88$eefd3600$ccf7a200$@olddog.co.uk> <533BC9AE.8020602@cisco.com> <061601cf4e9b$adb85570$09290050$@olddog.co.uk> <85DAD28B-6A14-4BEB-B324-816A0FFA347D@cisco.com> <CAG4d1rebTqG3Y7b8iDMTRSZJoCzyhomuCi4poAcohsPsc_Za3w@mail.gmail.com> <537A8F27.40205@cisco.com>
Date: Tue, 20 May 2014 15:06:58 -0400
Message-ID: <CAG4d1rfxVLdnkSQHGStye_m+-Nr=PxUak97TKwr79nSs8hsaZg@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Javed Asghar <jasghar@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/Na3oT1ZTrJx2l4kZ81ekTrlEkvA
Cc: draft-ietf-pim-explicit-rpf-vector.all@tools.ietf.org, pim@ietf.org, Alia Atlas <akatlas@juniper.net>
Subject: Re: [pim] AD review of draft-ietf-pim-explicit-rpf-vector
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 20 May 2014 19:07:02 -0000

Hi Javed,

Yes - I'm sorry for the delay (travel & sick).
If you and others can respond to my comments quickly, I can get this
into IETF Last Call before
Thurs so it will make the telechat after this one.

Comments from review:

Sec 10:  If the RPF vector isn't understood, isn't the path taken by
the traffic not going to conform to that desire?  I agree that the
possibility for loops is bad if the explicit RPF vector remained - but
I am also concerned that there's no way to tell that the desired path
wasn't taken - in terms of errors reported or so on.   I don't see a
protocol based way of forcing an error to be returned or capability
checking - so I'm expecting to see a small paragraph that talks about
the requirement in terms of manageability for computing the explicit
path and perhaps using mtrace to verify.   If you have a better
suggestion, I would love to see it.

I do feel that this mechanism is under-specified in the context of how
it is to be used.  For example, is make-before-break important?  What
about knowing that the new path is fully created before modifying the
other one for live-live?  How is any of this coordinated if there are
multiple leaf-nodes independently determining the explicit RPF vector
to use?  I do see Sec 7 discussing how to handle conflicts - but I
don't see any consideration of the dynamics of that solution or why it
is a good choice (beyond being a choice and in RFC 5384).

Nits:
Figure 1 - the figure is not properly aligned

Regards,
Alia


On Mon, May 19, 2014 at 7:09 PM, Javed Asghar <jasghar@cisco.com> wrote:
> Hi Alia,
>
> Did you get a chance to review? Its been awhile.
> If its ok, we'd like to move it forward.
>
> Thanks,
> -Javed.
>
>
> On 4/3/2014 3:11 PM, Alia Atlas wrote:
>
> Thanks for updating the draft.  I will review it very soon so we can get it
> moving along.
>
> Alia
>
>
> On Thu, Apr 3, 2014 at 9:07 AM, IJsbrand Wijnands <ice@cisco.com> wrote:
>>
>> Thanks Adrian,
>>
>> > Forwarded to Alia who now has the joy of being your AD.
>> >
>> > From me, just to note that you cannot demand a code point from IANA, you
>> > can only request one. The way to do it is to use the TBD form of the text I
>> > suggested and then say. "It is requested that IANA assign the value 4."
>>
>> We'll change it to say 'requested'.
>>
>> >
>> > Note for future reference that if you feel an attachment for a specific
>> > code point you really, really need to apply for an early allocation (RFC
>> > 7120) because someone else might come along in the intervening time and use
>> > your value for something else.
>>
>> Yes, we know about that. I remember discussing it with Stig at one point,
>> but since this was the only draft in the queue to request such value I think
>> the conclusion was that its not necessary to do early allocation, but your
>> right, we should really always do that to be safe.
>>
>> Thx,
>>
>> Ice.
>>
>>
>> >
>> > Adrian
>> >
>> > From: Javed Asghar [mailto:jasghar@cisco.com]
>> > Sent: 02 April 2014 09:26
>> > To: adrian@olddog.co.uk; draft-ietf-pim-explicit-rpf-vector
>> > Subject: Re: AD review of draft-ietf-pim-explicit-rpf-vector
>> >
>> > Hi,
>> >
>> > Submitted updated draft:
>> > http://www.ietf.org/internet-drafts/draft-ietf-pim-explicit-rpf-vector-04.txt
>> > Please see comments inline below.
>> >
>> > Cheers,
>> > -Javed.
>> >
>> >
>> > On 1/26/2014 3:22 AM, Adrian Farrel wrote:
>> > Hi,
>> >
>> > I have done my usual AD review of this document after receiving the
>> > publication request. The purpose of the review is to catch and fix
>> > any issues that might otherwise show up in IETF last call or IESG
>> > review. This helps smooth the passage of the document later and also
>> > increases the quality text.
>> >
>> > This seems like a good and simple proposal, and I don't want to bog
>> > it down. But there are a number of small editorial issues and a
>> > couple of technical questions included below.
>> >
>> > I have put the document into "Revised I-D Needed" state and will
>> > wait to see an updated version before I start the IETF last call.
>> > But please feel free to debate any of these points with me.
>> >
>> > Thanks for the work.
>> >
>> > Adrian
>> >
>> > ---
>> >
>> > You need to fix the idnits before I can put this to IETF last call.
>> >
>> > - Missing page breaks
>> > - 2119 boilerplate broken (you have "SHALL" "NOT")
>> > - there is a line too long
>> > - missing reference for [draft-mofrr-karan]
>> >
>> > [Shepherd - Your write-up says no nits found. How come?]
>> >
>> > ---
>> >
>> > Conventionally we have used the term "strict" in counterpoint to
>> > "loose" to describe hops, and termed the whole path "explicit". I
>> > don't suppose this matters: you are defining your own terms for a
>> > new application in PIM.
>> >
>> > However, this has led to some confusion in the text because of the
>> > normal use of the English word "explicit". For example, the Abstract
>> > says:
>> >    This document defines a new Reverse Path Forwarding (RPF) Vector
>> >    TLV to build multicast trees via an explicit path sent in the PIM
>> >    join.
>> > ...which doesn't give any clue to the distinction between this work
>> > and RFC 5496. You might be better with something like:
>> >    The PIM Reverse Path Forwarding (RPF) Vector TLV defined in RFC 5496
>> >    can be included in a PIM Join Attribute to allow a leaf to apply
>> >    controls to the path of a multicast tree. This document defines a
>> >    new Vector Attribute type so that an RPF Vector TLV can be used to
>> >    indicate that the unicast address indicated in the TLV must be used
>> >    as the next hop in the multicast tree.
>> >
>> > This kind of language could usefully be repeated throughout the
>> > document.
>> >
>> > JA>>> Updated
>> >
>> >
>> > ---
>> >
>> > Section 1
>> >
>> >    For some applications, it might be useful to have a way to specify
>> >    the explicit path along which the PIM join is propagated.
>> >
>> > Could you possibly be a little less vague? :-)
>> > If this is the level of certainty you have for the utility of your work
>> > then it shouldn't be on the Standards Track. Fortunately, you *do* have
>> > a good use case later in the document.
>> >
>> > I suggest re-ordering paragraphs:
>> >
>> > 3, 4, 2
>> >
>> > ...and delete paragraph 1.
>> >
>> > ---
>> >
>> > JA>>> Updated.
>> >
>> >
>> > Suggest to rename Section 3 "Motivation"
>> >
>> > ---
>> >
>> > JA>>> Updated
>> >
>> >
>> > Section 3
>> >
>> > As noted above, you need to provide the reference for
>> > [draft-mofrr-karan]. But actually, I wonder whether you really need to
>> > include the citation as the text in the paragraph seems to hold up well
>> > without any further explanation.
>> >
>> > ---
>> >
>> > JA>>> Updated.
>> >
>> >
>> > Section 3
>> >
>> >    It might be useful to have a way to specify the explicit path
>> >    along which the PIM join is propagated.
>> >
>> > I think you established that it *is* useful in the previous text.
>> >
>> > JA>>> Corrected.
>> >
>> >
>> > ---
>> >
>> > Section 3
>> >
>> >    How the Explicit RPF Vector list is determined is outside the
>> >    scope of this document. It may either be manually configured by
>> >    the network operator or procedures may be implemented on the
>> >    egress router to dynamically calculate the vector list based on
>> >    a link state database protocol, like OSPF or IS-IS.
>> >
>> > I agree that this should be out of scope and you should say so.
>> > However, having said it is out of scope, why do you go on to
>> > discuss it?
>> >
>> > JA>>> Ack. This is implementation specific. We have changed this
>> > discussion as example. This was feedback from previous reviews.
>> >
>> >
>> > ---
>> >
>> > You should give more clarity as to why an RPF list using 5496 list
>> > entries would not be good enough. In Figure 1 it would appear that the
>> > list {R4, R3, R6, R5, R2, R1} would work just fine using 5496.
>> >
>> > JA>>> Added more clarity with a comparison between Explicit RPF Vector
>> > and RFC5496 procedures.
>> >
>> >
>> > ---
>> >
>> > Section 5
>> >
>> >    This draft uses PIM join attribute type 4 for specifying an Explicit
>> >    RPF Vector.
>> >
>> > Please make this:
>> >
>> >    This draft uses PIM join attribute type TBD by IANA for specifying an
>> >    Explicit RPF Vector.
>> >
>> > ---
>> >
>> > JA>>> Updated.
>> >
>> >
>> > Section 7 is describing, for example, simple network with source S and
>> > leafs R1 and R2...
>> >
>> >   A   R1
>> >  / \ /
>> > S   C
>> >  \ / \
>> >   B   R2
>> >
>> > ...where R1 sends explicit RPF TLVs {C, A} and that path is set up.
>> > Then R2 sends explicit RPF TLVs {C, B}.
>> >
>> > Section 3.3.3 of RFC 5384 is cited as the tie-breaker.
>> > This is OK, but it appears to say that the Explicit RPF is not
>> > mandatory. It would be nice to make it very clear that a receiver has
>> > no expectations that the explicit RPF list it supplies will actually be
>> > used.
>> >
>> > JA>>> There is no change in our draft with respect to this behavior and
>> > its documented well in RFC 5384 section 3.3.3. Adding more text could
>> > confuse the reader. We felt the current text is sufficient. Let us know if
>> > this is ok with you.
>> >
>> >
>> > ---
>> >
>> > Section 10
>> >
>> > This is important material to include, but I think it needs some work.
>> >
>> >    The F bit MUST be set to 0 by a downstream router in the join that
>> >    is sent to the upstream router that does not support Explicit RPF
>> >    vector.
>> >
>> > But the downstream router doesn't know whether the upstream router
>> > supports the new vector or not! So I think you need...
>> >
>> >    The F bit MUST be set to 0 in all Explicit RPF vectors in case the
>> >    upstream router receiving the join does not support the TLV. As
>> >    described in section 3.3.2 of [RFC5384], routers that do not
>> >    understand the type of a particular attribute that has the F bit
>> >    clear will discard it and continue to process the join.
>> >
>> >    This processing is particularly important when the routers that
>> >    do not support the Explicit RPF TLV are identified as hops in the
>> >    explicit RPF list, because failing to remove the RPF vectors could
>> >    cause upstream routers to send the join back toward these routers
>> >    causing loops.
>> >
>> > JA>>> Updated. Thanks for the clarity. Its very precise.
>> >
>> >
>> >
>> > However, this doesn't seem to be the only way that loops can be caused
>> > (referring back to section 9).
>> > I don't see this mentioned in RFC 5496 either, but surely:
>> > - the RPF list could contain an explicit loop
>> > - the use of loose hops with poorly ordered list entries could create a
>> >   loop
>> >
>> > It is fine to note that this is caught by normal PIM processing, but
>> > you should say so, and you should say what happens to the join. It
>> > seems to me that 3.3.4 of 5496 only catches the case where join is
>> > targeting the same upstream neighbor. But the sequential list nature
>> > of the RPF list means that the loop might not be "endless" but could
>> > still be a loop. How is this caught and handled?
>> >
>> >
>> > JA>>> Please note that the explicit or loose RPF vector list at every
>> > hop will consume the RPF vector entry. If an explicit or loose RPF vector
>> > list is constructed poorly (eg. mis-config) the processing of the RPF vector
>> > is still as described in RFC 5496 and doesn't need to change. We need to fix
>> > the user error.
>> >
>> >
>> > ---
>> >
>> > Section 11
>> >
>> > Please replace...
>> >
>> > OLD
>> >    Type
>> >    ----
>> >    The Vector Attribute type is 4.
>> > NEW
>> >    Type
>> >    ----
>> >    The Vector Attribute type is TBD by IANA.
>> > END
>> >
>> > ---
>> >
>> > JA>>> We would like to request type 4 attribute from IANA explicitly.
>> >
>> >
>> > Section 13 seems light!
>> >
>> > The RPF list (and especially the explicit RPF) provides a way to
>> > cause traffic to take different routes through the network. This
>> > could be used to cause traffic to take expensive paths, to be
>> > routed through hot parts of the network, or to be directed to
>> > snooping nodes.
>> >
>> > This means that the existence of the RPF TLV makes the use of
>> > security in PIM more important to prevent tampering with the RPF
>> > list.
>> > JA>>> Good point.
>> >
>> >
>> > But it also raises a question of policy and authorization. Clearly,
>> > when a receiver seeks to join a multicast tree, it must be
>> > authenticated for that join. But additionally, you may want to note
>> > that the inclusion of an RPF list by a receiver should be subject to
>> > policy.
>> >
>> > JA>>> Updated.
>> >
>> >
>> > .
>> >
>> >
>>
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim
>
>
>


From nobody Wed May 21 00:46:57 2014
Return-Path: <tmmorin.orange@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D55D21A0830; Wed, 21 May 2014 00:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 gl68_uyn_xvo; Wed, 21 May 2014 00:46:26 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2F8E1A0829; Wed, 21 May 2014 00:46:24 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id q59so1647231wes.35 for <multiple recipients>; Wed, 21 May 2014 00:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:content-type:content-transfer-encoding; bh=ogGjmt+S0SmxWpR6lgKuySCxZ8wsugijcPT8VxW3QKA=; b=kX9dmV09i8XbpS2ET4lGdHk0klfYTgD7M695rnvAwuB9zcy+3LvAgASk0+1QNMiMBJ dIagEXlyXemBHtL/2ApCsWeODAjJcFeBbw+1VgDko5JeOXgNh33LGnAGT0ezgnaejsV5 bQKU84uLR4RB6d/BDaJO1gT2td0/OITlWI+opgSEQY57oASVxTMjeHkqIGo3OstSpojt sO7+UlAa7e381k3XLM4OPWfNSCC3ZX1HFgzPrs1aV8WGUvEFZrvtsrOSLwIxwLJhU1/w EMZYQ9GsdDCAof/9C8zBQjBlxLrVaWVc8W1E+iJu9SKS8eBbGDOQVB/6s8z1Yhd98NQl iGoQ==
X-Received: by 10.194.77.72 with SMTP id q8mr312701wjw.82.1400658383078; Wed, 21 May 2014 00:46:23 -0700 (PDT)
Received: from [127.0.0.1] (ARennes-652-1-10-91.w2-10.abo.wanadoo.fr. [2.10.129.91]) by mx.google.com with ESMTPSA id dk10sm448355wib.1.2014.05.21.00.46.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 21 May 2014 00:46:22 -0700 (PDT)
Sender: Thomas Morin <tmmorin.orange@gmail.com>
Message-ID: <537C59CB.2010105@orange.com>
Date: Wed, 21 May 2014 09:46:19 +0200
From: Thomas Morin <thomas.morin@orange.com>
Organization: Orange
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: l3vpn@ietf.org, mboned@ietf.org, pim@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/YzwUNvGPzdUJ8X-SsRrqaGN5WrQ
Cc: draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org
Subject: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 21 May 2014 07:46:29 -0000

Hello,

This email starts a two-week poll on adopting
draft-zzhang-l3vpn-mvpn-global-table-mcast-04 [1] as a working group 
item of the l3vpn working group.

Note well that the mboned and pim working group are included in this 
poll, to facilitate feedback from these working groups on this topic of 
multicast routing in the global routing table.

Please send comments to the l3vpn mailing-list and state if you support 
adoption or not (in the later case, please also state the reasons).

This poll runs until June 5th.



*Coincidentally*, we are also polling for knowledge of any IPR that
applies to this draft, to ensure that IPR has been disclosed in
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669
and 5378 for more details).

==> *If you are listed as a document author or contributor* please
respond to this email and indicate whether or not you are aware of any 
relevant IPR.

The draft will not be adopted until a response has been received from
each author and contributor.

If you are not listed as an author or contributor, then please 
explicitly respond only if you are aware of any IPR that has not yet 
been disclosed in conformance with IETF rules.

Thank you,

Martin & Thomas
l3vpn co-chairs

[1] http://tools.ietf.org/html/draft-zzhang-l3vpn-mvpn-global-table-mcast-04


From nobody Wed May 21 06:34:14 2014
Return-Path: <lenny@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D654D1A067E; Wed, 21 May 2014 06:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 vYBohVSHQtzy; Wed, 21 May 2014 06:34:11 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CE0C1A067C; Wed, 21 May 2014 06:34:11 -0700 (PDT)
Received: from BY2PR05CA035.namprd05.prod.outlook.com (10.141.250.25) by BY2PR05MB110.namprd05.prod.outlook.com (10.242.38.21) with Microsoft SMTP Server (TLS) id 15.0.944.11; Wed, 21 May 2014 13:34:08 +0000
Received: from BL2FFO11FD008.protection.gbl (2a01:111:f400:7c09::146) by BY2PR05CA035.outlook.office365.com (2a01:111:e400:2c5f::25) with Microsoft SMTP Server (TLS) id 15.0.944.11 via Frontend Transport; Wed, 21 May 2014 13:34:08 +0000
Received: from o365mail.juniper.net (207.17.137.149) by BL2FFO11FD008.mail.protection.outlook.com (10.173.161.4) with Microsoft SMTP Server (TLS) id 15.0.949.9 via Frontend Transport; Wed, 21 May 2014 13:34:08 +0000
Received: from P-EMF03-SAC.jnpr.net (172.24.192.19) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 21 May 2014 06:33:33 -0700
Received: from magenta.juniper.net (172.17.27.123) by P-EMF03-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 21 May 2014 06:33:29 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id s4LDXRn38170; Wed, 21 May 2014 06:33:28 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 091171144F;  Wed, 21 May 2014 06:33:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id F127E11446;	Wed, 21 May 2014 06:33:25 -0700 (PDT)
Date: Wed, 21 May 2014 06:33:25 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Thomas Morin <thomas.morin@orange.com>
In-Reply-To: <537C59CB.2010105@orange.com>
Message-ID: <20140521063302.A15332@eng-mail01.juniper.net>
References: <537C59CB.2010105@orange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:207.17.137.149; CTRY:US; IPV:CAL; IPV:NLI; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(6009001)(189002)(199002)(24454002)(102836001)(76482001)(74502001)(80022001)(79102001)(47776003)(81342001)(15975445006)(46102001)(44976005)(21056001)(92566001)(77982001)(20776003)(4396001)(74662001)(64706001)(81542001)(33656002)(50986999)(26826002)(54356999)(87936001)(31966008)(77096999)(23726002)(50466002)(46406003)(86362001)(6806004)(85852003)(92726001)(83072002)(15202345003)(76176999)(46386002)(83322001)(57986005)(99396002)(45336002)(19580395003)(42262001)(90966001); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB110; H:o365mail.juniper.net; FPR:; MLV:ovrnspm; PTR:p-cldedg02-hq.juniper.net; MX:1; A:1; LANG:en; 
X-Forefront-PRVS: 0218A015FA
Received-SPF: SoftFail (: domain of transitioning juniper.net discourages use of 207.17.137.149 as permitted sender)
Authentication-Results: spf=softfail (sender IP is 207.17.137.149) smtp.mailfrom=lenny@juniper.net; 
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/4xTXP7KybwqMEQuaD3hsuShfShs
Cc: mboned@ietf.org, draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org, l3vpn@ietf.org, pim@ietf.org
Subject: Re: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 21 May 2014 13:34:13 -0000

I'm not aware of any relevant IPR.

-Lenny

On Wed, 21 May 2014, Thomas Morin wrote:

| Hello,
| 
| This email starts a two-week poll on adopting
| draft-zzhang-l3vpn-mvpn-global-table-mcast-04 [1] as a working group item of
| the l3vpn working group.
| 
| Note well that the mboned and pim working group are included in this poll, to
| facilitate feedback from these working groups on this topic of multicast
| routing in the global routing table.
| 
| Please send comments to the l3vpn mailing-list and state if you support
| adoption or not (in the later case, please also state the reasons).
| 
| This poll runs until June 5th.
| 
| 
| 
| *Coincidentally*, we are also polling for knowledge of any IPR that
| applies to this draft, to ensure that IPR has been disclosed in
| compliance with IETF IPR rules (see RFCs 3979, 4879, 3669
| and 5378 for more details).
| 
| ==> *If you are listed as a document author or contributor* please
| respond to this email and indicate whether or not you are aware of any
| relevant IPR.
| 
| The draft will not be adopted until a response has been received from
| each author and contributor.
| 
| If you are not listed as an author or contributor, then please explicitly
| respond only if you are aware of any IPR that has not yet been disclosed in
| conformance with IETF rules.
| 
| Thank you,
| 
| Martin & Thomas
| l3vpn co-chairs
| 
| [1] http://tools.ietf.org/html/draft-zzhang-l3vpn-mvpn-global-table-mcast-04
| 


From nobody Wed May 21 06:35:11 2014
Return-Path: <yakov@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 849CA1A067E; Wed, 21 May 2014 06:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 UwChLND6jjCb; Wed, 21 May 2014 06:35:06 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0238.outbound.protection.outlook.com [207.46.163.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 839FD1A06A0; Wed, 21 May 2014 06:35:01 -0700 (PDT)
Received: from BL2PR05MB210.namprd05.prod.outlook.com (10.242.198.145) by BL2PR05MB212.namprd05.prod.outlook.com (10.242.198.150) with Microsoft SMTP Server (TLS) id 15.0.944.11; Wed, 21 May 2014 13:34:59 +0000
Received: from BL2PR05MB210.namprd05.prod.outlook.com ([169.254.6.51]) by BL2PR05MB210.namprd05.prod.outlook.com ([169.254.6.51]) with mapi id 15.00.0944.000; Wed, 21 May 2014 13:34:58 +0000
From: Yakov Rekhter <yakov@juniper.net>
To: "EXT - thomas.morin@orange.com" <thomas.morin@orange.com>, "l3vpn@ietf.org" <l3vpn@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
Thread-Index: AQHPdMjofUr+q/fVYEqBghJMmCHiw5tLCUSg
Date: Wed, 21 May 2014 13:34:57 +0000
Message-ID: <b44114906b684f5492d5d9510839c7bc@BL2PR05MB210.namprd05.prod.outlook.com>
References: <537C59CB.2010105@orange.com>
In-Reply-To: <537C59CB.2010105@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.239.14]
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(428001)(199002)(189002)(377454003)(51704005)(13464003)(76482001)(74662001)(74502001)(81342001)(81542001)(76576001)(2656002)(46102001)(101416001)(4396001)(85852003)(66066001)(77982001)(83072002)(2201001)(33646001)(87936001)(15975445006)(80022001)(99286001)(79102001)(21056001)(20776003)(76176999)(54356999)(50986999)(15202345003)(64706001)(99396002)(83322001)(19580405001)(19580395003)(86362001)(74316001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR05MB212; H:BL2PR05MB210.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (: juniper.net does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=yakov@juniper.net; 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/pVWBFJdxZAhUNZoKDMKofWf3nEs
Cc: "draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org" <draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org>
Subject: Re: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 21 May 2014 13:35:08 -0000

VGhvbWFzLA0KDQpJIHN1cHBvcnQgdGhlIGFkb3B0aW9uLg0KDQpZYWtvdi4NCg0KPiAtLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBMM1ZQTiBbbWFpbHRvOmwzdnBuLWJvdW5jZXNA
aWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBUaG9tYXMgTW9yaW4NCj4gU2VudDogV2VkbmVzZGF5LCBN
YXkgMjEsIDIwMTQgMzo0NiBBTQ0KPiBUbzogbDN2cG5AaWV0Zi5vcmc7IG1ib25lZEBpZXRmLm9y
ZzsgcGltQGlldGYub3JnDQo+IENjOiBkcmFmdC16emhhbmctbDN2cG4tbXZwbi1nbG9iYWwtdGFi
bGUtbWNhc3RAdG9vbHMuaWV0Zi5vcmcNCj4gU3ViamVjdDogUG9sbCBmb3IgYWRvcHRpb246IGRy
YWZ0LXp6aGFuZy1sM3Zwbi1tdnBuLWdsb2JhbC10YWJsZS1tY2FzdC0NCj4gMDQNCj4gDQo+IEhl
bGxvLA0KPiANCj4gVGhpcyBlbWFpbCBzdGFydHMgYSB0d28td2VlayBwb2xsIG9uIGFkb3B0aW5n
DQo+IGRyYWZ0LXp6aGFuZy1sM3Zwbi1tdnBuLWdsb2JhbC10YWJsZS1tY2FzdC0wNCBbMV0gYXMg
YSB3b3JraW5nIGdyb3VwDQo+IGl0ZW0gb2YgdGhlIGwzdnBuIHdvcmtpbmcgZ3JvdXAuDQo+IA0K
PiBOb3RlIHdlbGwgdGhhdCB0aGUgbWJvbmVkIGFuZCBwaW0gd29ya2luZyBncm91cCBhcmUgaW5j
bHVkZWQgaW4gdGhpcw0KPiBwb2xsLCB0byBmYWNpbGl0YXRlIGZlZWRiYWNrIGZyb20gdGhlc2Ug
d29ya2luZyBncm91cHMgb24gdGhpcyB0b3BpYyBvZg0KPiBtdWx0aWNhc3Qgcm91dGluZyBpbiB0
aGUgZ2xvYmFsIHJvdXRpbmcgdGFibGUuDQo+IA0KPiBQbGVhc2Ugc2VuZCBjb21tZW50cyB0byB0
aGUgbDN2cG4gbWFpbGluZy1saXN0IGFuZCBzdGF0ZSBpZiB5b3Ugc3VwcG9ydA0KPiBhZG9wdGlv
biBvciBub3QgKGluIHRoZSBsYXRlciBjYXNlLCBwbGVhc2UgYWxzbyBzdGF0ZSB0aGUgcmVhc29u
cykuDQo+IA0KPiBUaGlzIHBvbGwgcnVucyB1bnRpbCBKdW5lIDV0aC4NCj4gDQo+IA0KPiANCj4g
KkNvaW5jaWRlbnRhbGx5Kiwgd2UgYXJlIGFsc28gcG9sbGluZyBmb3Iga25vd2xlZGdlIG9mIGFu
eSBJUFIgdGhhdA0KPiBhcHBsaWVzIHRvIHRoaXMgZHJhZnQsIHRvIGVuc3VyZSB0aGF0IElQUiBo
YXMgYmVlbiBkaXNjbG9zZWQgaW4NCj4gY29tcGxpYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzIChz
ZWUgUkZDcyAzOTc5LCA0ODc5LCAzNjY5IGFuZCA1Mzc4IGZvcg0KPiBtb3JlIGRldGFpbHMpLg0K
PiANCj4gPT0+ICpJZiB5b3UgYXJlIGxpc3RlZCBhcyBhIGRvY3VtZW50IGF1dGhvciBvciBjb250
cmlidXRvciogcGxlYXNlDQo+IHJlc3BvbmQgdG8gdGhpcyBlbWFpbCBhbmQgaW5kaWNhdGUgd2hl
dGhlciBvciBub3QgeW91IGFyZSBhd2FyZSBvZiBhbnkNCj4gcmVsZXZhbnQgSVBSLg0KPiANCj4g
VGhlIGRyYWZ0IHdpbGwgbm90IGJlIGFkb3B0ZWQgdW50aWwgYSByZXNwb25zZSBoYXMgYmVlbiBy
ZWNlaXZlZCBmcm9tDQo+IGVhY2ggYXV0aG9yIGFuZCBjb250cmlidXRvci4NCj4gDQo+IElmIHlv
dSBhcmUgbm90IGxpc3RlZCBhcyBhbiBhdXRob3Igb3IgY29udHJpYnV0b3IsIHRoZW4gcGxlYXNl
DQo+IGV4cGxpY2l0bHkgcmVzcG9uZCBvbmx5IGlmIHlvdSBhcmUgYXdhcmUgb2YgYW55IElQUiB0
aGF0IGhhcyBub3QgeWV0DQo+IGJlZW4gZGlzY2xvc2VkIGluIGNvbmZvcm1hbmNlIHdpdGggSUVU
RiBydWxlcy4NCj4gDQo+IFRoYW5rIHlvdSwNCj4gDQo+IE1hcnRpbiAmIFRob21hcw0KPiBsM3Zw
biBjby1jaGFpcnMNCj4gDQo+IFsxXSBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC16
emhhbmctbDN2cG4tbXZwbi1nbG9iYWwtdGFibGUtDQo+IG1jYXN0LTA0DQoNCg==


From nobody Wed May 21 07:22:04 2014
Return-Path: <zzhang@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B45BA1A044B; Wed, 21 May 2014 07:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 1TP98hFC16KF; Wed, 21 May 2014 07:21:51 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0184.outbound.protection.outlook.com [207.46.163.184]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C2F51A03DD; Wed, 21 May 2014 07:21:51 -0700 (PDT)
Received: from BY2PR05MB079.namprd05.prod.outlook.com (10.242.38.16) by BY2PR05MB582.namprd05.prod.outlook.com (10.141.219.146) with Microsoft SMTP Server (TLS) id 15.0.944.11; Wed, 21 May 2014 14:21:48 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.229]) by BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.229]) with mapi id 15.00.0944.000; Wed, 21 May 2014 14:21:47 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: Lenny Giuliano <lenny@juniper.net>, "EXT - thomas.morin@orange.com" <thomas.morin@orange.com>
Thread-Topic: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
Thread-Index: AQHPdMkO/eNDRn2GX02FDmWJrHsSUJtLCOmAgAANa+A=
Date: Wed, 21 May 2014 14:21:46 +0000
Message-ID: <a768f9216cce4634bc56f905ac3f6f28@BY2PR05MB079.namprd05.prod.outlook.com>
References: <537C59CB.2010105@orange.com> <20140521063302.A15332@eng-mail01.juniper.net>
In-Reply-To: <20140521063302.A15332@eng-mail01.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(428001)(377454003)(51704005)(13464003)(24454002)(189002)(199002)(87936001)(79102001)(64706001)(19580395003)(33646001)(19580405001)(224303002)(4396001)(46102001)(15975445006)(76176999)(20776003)(81342001)(2656002)(77982001)(54356999)(76482001)(80022001)(86362001)(99286001)(66066001)(74662001)(83072002)(85852003)(92566001)(1941001)(50986999)(15202345003)(74316001)(81542001)(31966008)(21056001)(74502001)(76576001)(101416001)(99396002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB582; H:BY2PR05MB079.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (: juniper.net does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=zzhang@juniper.net; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/DyBCyZFYHjDuwKx9HTkCz8eck4w
Cc: "mboned@ietf.org" <mboned@ietf.org>, "draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org" <draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 21 May 2014 14:21:53 -0000

Me neither.

> -----Original Message-----
> From: pim [mailto:pim-bounces@ietf.org] On Behalf Of Leonard Giuliano
> Sent: Wednesday, May 21, 2014 9:33 AM
> To: EXT - thomas.morin@orange.com
> Cc: mboned@ietf.org; draft-zzhang-l3vpn-mvpn-global-table-
> mcast@tools.ietf.org; l3vpn@ietf.org; pim@ietf.org
> Subject: Re: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-
> table-mcast-04
>=20
>=20
> I'm not aware of any relevant IPR.
>=20
> -Lenny
>=20
> On Wed, 21 May 2014, Thomas Morin wrote:
>=20
> | Hello,
> |
> | This email starts a two-week poll on adopting
> | draft-zzhang-l3vpn-mvpn-global-table-mcast-04 [1] as a working group
> item of
> | the l3vpn working group.
> |
> | Note well that the mboned and pim working group are included in this
> poll, to
> | facilitate feedback from these working groups on this topic of
> multicast
> | routing in the global routing table.
> |
> | Please send comments to the l3vpn mailing-list and state if you
> support
> | adoption or not (in the later case, please also state the reasons).
> |
> | This poll runs until June 5th.
> |
> |
> |
> | *Coincidentally*, we are also polling for knowledge of any IPR that
> | applies to this draft, to ensure that IPR has been disclosed in
> | compliance with IETF IPR rules (see RFCs 3979, 4879, 3669
> | and 5378 for more details).
> |
> | =3D=3D> *If you are listed as a document author or contributor* please
> | respond to this email and indicate whether or not you are aware of any
> | relevant IPR.
> |
> | The draft will not be adopted until a response has been received from
> | each author and contributor.
> |
> | If you are not listed as an author or contributor, then please
> explicitly
> | respond only if you are aware of any IPR that has not yet been
> disclosed in
> | conformance with IETF rules.
> |
> | Thank you,
> |
> | Martin & Thomas
> | l3vpn co-chairs
> |
> | [1] http://tools.ietf.org/html/draft-zzhang-l3vpn-mvpn-global-table-
> mcast-04
> |
>=20
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From nobody Wed May 21 11:23:11 2014
Return-Path: <erosen@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F6231A01D5; Wed, 21 May 2014 11:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 lP--btx-Ywbh; Wed, 21 May 2014 11:23:03 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 051491A0152; Wed, 21 May 2014 11:23:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=193; q=dns/txt; s=iport; t=1400696582; x=1401906182; h=from:to:cc:subject:in-reply-to:reply-to:date:message-id; bh=fjC35h/5kkhpzk06UMZrUfKAznuLVkfOyWNWulDSCvk=; b=UDb2mcmexQR4n12sG6lK1SGnP4mBF6LoVcnYC6N/0c8ZaFyL9jdCVKzG 9ETqaVT5QdHzupHdKAioqSwDsErCSGfXLasbxl6jRDdVpIXDjZ2q6UP8v SU/dPt3bZkwwKXVOXvmaXDVXNYJ700FXXf5rt7wIhgUntdx7Ot2yXMhAX Q=;
X-IronPort-AV: E=Sophos;i="4.98,881,1392163200"; d="scan'208";a="326795648"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-3.cisco.com with ESMTP; 21 May 2014 18:23:02 +0000
Received: from erosen-lnx.cisco.com (erosen-lnx.cisco.com [161.44.71.19]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id s4LIN1WM019435; Wed, 21 May 2014 18:23:01 GMT
Received: from erosen-lnx (localhost [127.0.0.1]) by erosen-lnx.cisco.com (Postfix) with ESMTP id 590E14C; Wed, 21 May 2014 14:23:01 -0400 (EDT)
From: Eric Rosen <erosen@cisco.com>
To: Thomas Morin <thomas.morin@orange.com>
In-reply-to: Your message of Wed, 21 May 2014 09:46:19 +0200. <537C59CB.2010105@orange.com>
Date: Wed, 21 May 2014 14:23:01 -0400
Message-ID: <14746.1400696581@erosen-lnx>
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/dx0wItPbEVBLCh_7YV5a8JLGEeI
Cc: mboned@ietf.org, draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org, l3vpn@ietf.org, pim@ietf.org
Subject: Re: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: erosen@cisco.com
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: <http://www.ietf.org/mail-archive/web/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, 21 May 2014 18:23:04 -0000

> If you are listed as a document author or contributor please respond to
> this email and indicate whether or not you are aware of any relevant IPR.

I am not aware of any relevant IPR.



From nobody Wed May 21 17:40:31 2014
Return-Path: <lizhenbin@huawei.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDE1E1A000E; Wed, 21 May 2014 17:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.437
X-Spam-Level: *
X-Spam-Status: No, score=1.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 nF76fLjKxjoe; Wed, 21 May 2014 17:40:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C132A1A000B; Wed, 21 May 2014 17:40:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BEK12595; Thu, 22 May 2014 00:40:22 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 22 May 2014 01:40:10 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 22 May 2014 01:40:21 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.207]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Thu, 22 May 2014 08:40:17 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, Lenny Giuliano <lenny@juniper.net>, "EXT - thomas.morin@orange.com" <thomas.morin@orange.com>
Thread-Topic: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
Thread-Index: AQHPdPll0+1E80QthUawKfVa49WT+ptKj+4AgAEypCA=
Date: Thu, 22 May 2014 00:40:15 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D08218DDF@nkgeml506-mbx.china.huawei.com>
References: <537C59CB.2010105@orange.com> <20140521063302.A15332@eng-mail01.juniper.net> <a768f9216cce4634bc56f905ac3f6f28@BY2PR05MB079.namprd05.prod.outlook.com>
In-Reply-To: <a768f9216cce4634bc56f905ac3f6f28@BY2PR05MB079.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.76.77]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/bxBDLNBM7KfCPyjBztOkNsSnqus
Cc: "mboned@ietf.org" <mboned@ietf.org>, "draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org" <draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org>, "l3vpn@ietf.org" <l3vpn@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Subject: [pim] =?gb2312?b?tPC4tDogIFBvbGwgZm9yIGFkb3B0aW9uOiBkcmFmdC16emhh?= =?gb2312?b?bmctbDN2cG4tbXZwbi1nbG9iYWwtdGFibGUtbWNhc3QtMDQ=?=
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 22 May 2014 00:40:29 -0000

SSdtIG5vdCBhd2FyZSBvZiBhbnkgcmVsZXZhbnQgSVBSLg0KDQoNCi0tIFpoZW5iaW4oUm9iaW4p
DQoNCg0KDQotLS0tLdPKvP7Urbz+LS0tLS0NCreivP7IyzogTDNWUE4gW21haWx0bzpsM3Zwbi1i
b3VuY2VzQGlldGYub3JnXSC0+rHtIEplZmZyZXkgKFpoYW9odWkpIFpoYW5nDQq3osvNyrG85Dog
MjAxNMTqNdTCMjHI1SAyMjoyMg0KytW8/sjLOiBMZW5ueSBHaXVsaWFubzsgRVhUIC0gdGhvbWFz
Lm1vcmluQG9yYW5nZS5jb20NCrOty806IG1ib25lZEBpZXRmLm9yZzsgZHJhZnQtenpoYW5nLWwz
dnBuLW12cG4tZ2xvYmFsLXRhYmxlLW1jYXN0QHRvb2xzLmlldGYub3JnOyBsM3ZwbkBpZXRmLm9y
ZzsgcGltQGlldGYub3JnDQrW98ziOiBSRTogW3BpbV0gUG9sbCBmb3IgYWRvcHRpb246IGRyYWZ0
LXp6aGFuZy1sM3Zwbi1tdnBuLWdsb2JhbC10YWJsZS1tY2FzdC0wNA0KDQpNZSBuZWl0aGVyLg0K
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHBpbSBbbWFpbHRvOnBpbS1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgTGVvbmFyZCBHaXVsaWFubw0KPiBTZW50OiBX
ZWRuZXNkYXksIE1heSAyMSwgMjAxNCA5OjMzIEFNDQo+IFRvOiBFWFQgLSB0aG9tYXMubW9yaW5A
b3JhbmdlLmNvbQ0KPiBDYzogbWJvbmVkQGlldGYub3JnOyBkcmFmdC16emhhbmctbDN2cG4tbXZw
bi1nbG9iYWwtdGFibGUtDQo+IG1jYXN0QHRvb2xzLmlldGYub3JnOyBsM3ZwbkBpZXRmLm9yZzsg
cGltQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbcGltXSBQb2xsIGZvciBhZG9wdGlvbjogZHJh
ZnQtenpoYW5nLWwzdnBuLW12cG4tZ2xvYmFsLQ0KPiB0YWJsZS1tY2FzdC0wNA0KPiANCj4gDQo+
IEknbSBub3QgYXdhcmUgb2YgYW55IHJlbGV2YW50IElQUi4NCj4gDQo+IC1MZW5ueQ0KPiANCj4g
T24gV2VkLCAyMSBNYXkgMjAxNCwgVGhvbWFzIE1vcmluIHdyb3RlOg0KPiANCj4gfCBIZWxsbywN
Cj4gfA0KPiB8IFRoaXMgZW1haWwgc3RhcnRzIGEgdHdvLXdlZWsgcG9sbCBvbiBhZG9wdGluZw0K
PiB8IGRyYWZ0LXp6aGFuZy1sM3Zwbi1tdnBuLWdsb2JhbC10YWJsZS1tY2FzdC0wNCBbMV0gYXMg
YSB3b3JraW5nIGdyb3VwDQo+IGl0ZW0gb2YNCj4gfCB0aGUgbDN2cG4gd29ya2luZyBncm91cC4N
Cj4gfA0KPiB8IE5vdGUgd2VsbCB0aGF0IHRoZSBtYm9uZWQgYW5kIHBpbSB3b3JraW5nIGdyb3Vw
IGFyZSBpbmNsdWRlZCBpbiB0aGlzDQo+IHBvbGwsIHRvDQo+IHwgZmFjaWxpdGF0ZSBmZWVkYmFj
ayBmcm9tIHRoZXNlIHdvcmtpbmcgZ3JvdXBzIG9uIHRoaXMgdG9waWMgb2YNCj4gbXVsdGljYXN0
DQo+IHwgcm91dGluZyBpbiB0aGUgZ2xvYmFsIHJvdXRpbmcgdGFibGUuDQo+IHwNCj4gfCBQbGVh
c2Ugc2VuZCBjb21tZW50cyB0byB0aGUgbDN2cG4gbWFpbGluZy1saXN0IGFuZCBzdGF0ZSBpZiB5
b3UNCj4gc3VwcG9ydA0KPiB8IGFkb3B0aW9uIG9yIG5vdCAoaW4gdGhlIGxhdGVyIGNhc2UsIHBs
ZWFzZSBhbHNvIHN0YXRlIHRoZSByZWFzb25zKS4NCj4gfA0KPiB8IFRoaXMgcG9sbCBydW5zIHVu
dGlsIEp1bmUgNXRoLg0KPiB8DQo+IHwNCj4gfA0KPiB8ICpDb2luY2lkZW50YWxseSosIHdlIGFy
ZSBhbHNvIHBvbGxpbmcgZm9yIGtub3dsZWRnZSBvZiBhbnkgSVBSIHRoYXQgDQo+IHwgYXBwbGll
cyB0byB0aGlzIGRyYWZ0LCB0byBlbnN1cmUgdGhhdCBJUFIgaGFzIGJlZW4gZGlzY2xvc2VkIGlu
IA0KPiB8IGNvbXBsaWFuY2Ugd2l0aCBJRVRGIElQUiBydWxlcyAoc2VlIFJGQ3MgMzk3OSwgNDg3
OSwgMzY2OSBhbmQgNTM3OCANCj4gfCBmb3IgbW9yZSBkZXRhaWxzKS4NCj4gfA0KPiB8ID09PiAq
SWYgeW91IGFyZSBsaXN0ZWQgYXMgYSBkb2N1bWVudCBhdXRob3Igb3IgY29udHJpYnV0b3IqIHBs
ZWFzZSANCj4gfCByZXNwb25kIHRvIHRoaXMgZW1haWwgYW5kIGluZGljYXRlIHdoZXRoZXIgb3Ig
bm90IHlvdSBhcmUgYXdhcmUgb2YgDQo+IHwgYW55IHJlbGV2YW50IElQUi4NCj4gfA0KPiB8IFRo
ZSBkcmFmdCB3aWxsIG5vdCBiZSBhZG9wdGVkIHVudGlsIGEgcmVzcG9uc2UgaGFzIGJlZW4gcmVj
ZWl2ZWQgDQo+IHwgZnJvbSBlYWNoIGF1dGhvciBhbmQgY29udHJpYnV0b3IuDQo+IHwNCj4gfCBJ
ZiB5b3UgYXJlIG5vdCBsaXN0ZWQgYXMgYW4gYXV0aG9yIG9yIGNvbnRyaWJ1dG9yLCB0aGVuIHBs
ZWFzZQ0KPiBleHBsaWNpdGx5DQo+IHwgcmVzcG9uZCBvbmx5IGlmIHlvdSBhcmUgYXdhcmUgb2Yg
YW55IElQUiB0aGF0IGhhcyBub3QgeWV0IGJlZW4NCj4gZGlzY2xvc2VkIGluDQo+IHwgY29uZm9y
bWFuY2Ugd2l0aCBJRVRGIHJ1bGVzLg0KPiB8DQo+IHwgVGhhbmsgeW91LA0KPiB8DQo+IHwgTWFy
dGluICYgVGhvbWFzDQo+IHwgbDN2cG4gY28tY2hhaXJzDQo+IHwNCj4gfCBbMV0gaHR0cDovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtenpoYW5nLWwzdnBuLW12cG4tZ2xvYmFsLXRhYmxlLQ0K
PiBtY2FzdC0wNA0KPiB8DQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KPiBwaW0gbWFpbGluZyBsaXN0DQo+IHBpbUBpZXRmLm9yZw0KPiBodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbQ0KDQo=


From nobody Wed May 21 17:44:00 2014
Return-Path: <lizhenbin@huawei.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05F121A000B; Wed, 21 May 2014 17:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.437
X-Spam-Level: *
X-Spam-Status: No, score=1.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 gU_GXXMAGbbA; Wed, 21 May 2014 17:43:49 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCD881A0007; Wed, 21 May 2014 17:43:48 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHB14204; Thu, 22 May 2014 00:43:46 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 22 May 2014 01:43:33 +0100
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 22 May 2014 01:43:45 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.207]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Thu, 22 May 2014 08:43:40 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Thomas Morin <thomas.morin@orange.com>, "l3vpn@ietf.org" <l3vpn@ietf.org>,  "mboned@ietf.org" <mboned@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] Poll for adoption: draft-zzhang-l3vpn-mvpn-global-table-mcast-04
Thread-Index: AQHPdMkWRVy2LgczfkirtdW2EuRZZptLw0OQ
Date: Thu, 22 May 2014 00:43:39 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D08218DF9@nkgeml506-mbx.china.huawei.com>
References: <537C59CB.2010105@orange.com>
In-Reply-To: <537C59CB.2010105@orange.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.76.77]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/_JxSuRvctNFiNcweM4wdvKKCAoQ
Cc: "draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org" <draft-zzhang-l3vpn-mvpn-global-table-mcast@tools.ietf.org>
Subject: [pim] =?gb2312?b?tPC4tDogIFBvbGwgZm9yIGFkb3B0aW9uOglkcmFmdC16emhh?= =?gb2312?b?bmctbDN2cG4tbXZwbi1nbG9iYWwtdGFibGUtbWNhc3QtMDQ=?=
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 22 May 2014 00:43:51 -0000

U3VwcG9ydCBhcyB0aGUgY29udHJpYnV0b3IuIA0KDQotLVpoZW5iaW4oUm9iaW4pDQoNCg0KDQoN
Ci0tLS0t08q8/tStvP4tLS0tLQ0Kt6K8/sjLOiBwaW0gW21haWx0bzpwaW0tYm91bmNlc0BpZXRm
Lm9yZ10gtPqx7SBUaG9tYXMgTW9yaW4NCreiy83KsbzkOiAyMDE0xOo11MIyMcjVIDE1OjQ2DQrK
1bz+yMs6IGwzdnBuQGlldGYub3JnOyBtYm9uZWRAaWV0Zi5vcmc7IHBpbUBpZXRmLm9yZw0Ks63L
zTogZHJhZnQtenpoYW5nLWwzdnBuLW12cG4tZ2xvYmFsLXRhYmxlLW1jYXN0QHRvb2xzLmlldGYu
b3JnDQrW98ziOiBbcGltXSBQb2xsIGZvciBhZG9wdGlvbjogZHJhZnQtenpoYW5nLWwzdnBuLW12
cG4tZ2xvYmFsLXRhYmxlLW1jYXN0LTA0DQoNCkhlbGxvLA0KDQpUaGlzIGVtYWlsIHN0YXJ0cyBh
IHR3by13ZWVrIHBvbGwgb24gYWRvcHRpbmcNCmRyYWZ0LXp6aGFuZy1sM3Zwbi1tdnBuLWdsb2Jh
bC10YWJsZS1tY2FzdC0wNCBbMV0gYXMgYSB3b3JraW5nIGdyb3VwIGl0ZW0gb2YgdGhlIGwzdnBu
IHdvcmtpbmcgZ3JvdXAuDQoNCk5vdGUgd2VsbCB0aGF0IHRoZSBtYm9uZWQgYW5kIHBpbSB3b3Jr
aW5nIGdyb3VwIGFyZSBpbmNsdWRlZCBpbiB0aGlzIHBvbGwsIHRvIGZhY2lsaXRhdGUgZmVlZGJh
Y2sgZnJvbSB0aGVzZSB3b3JraW5nIGdyb3VwcyBvbiB0aGlzIHRvcGljIG9mIG11bHRpY2FzdCBy
b3V0aW5nIGluIHRoZSBnbG9iYWwgcm91dGluZyB0YWJsZS4NCg0KUGxlYXNlIHNlbmQgY29tbWVu
dHMgdG8gdGhlIGwzdnBuIG1haWxpbmctbGlzdCBhbmQgc3RhdGUgaWYgeW91IHN1cHBvcnQgYWRv
cHRpb24gb3Igbm90IChpbiB0aGUgbGF0ZXIgY2FzZSwgcGxlYXNlIGFsc28gc3RhdGUgdGhlIHJl
YXNvbnMpLg0KDQpUaGlzIHBvbGwgcnVucyB1bnRpbCBKdW5lIDV0aC4NCg0KDQoNCipDb2luY2lk
ZW50YWxseSosIHdlIGFyZSBhbHNvIHBvbGxpbmcgZm9yIGtub3dsZWRnZSBvZiBhbnkgSVBSIHRo
YXQgYXBwbGllcyB0byB0aGlzIGRyYWZ0LCB0byBlbnN1cmUgdGhhdCBJUFIgaGFzIGJlZW4gZGlz
Y2xvc2VkIGluIGNvbXBsaWFuY2Ugd2l0aCBJRVRGIElQUiBydWxlcyAoc2VlIFJGQ3MgMzk3OSwg
NDg3OSwgMzY2OSBhbmQgNTM3OCBmb3IgbW9yZSBkZXRhaWxzKS4NCg0KPT0+ICpJZiB5b3UgYXJl
IGxpc3RlZCBhcyBhIGRvY3VtZW50IGF1dGhvciBvciBjb250cmlidXRvciogcGxlYXNlIHJlc3Bv
bmQgdG8gdGhpcyBlbWFpbCBhbmQgaW5kaWNhdGUgd2hldGhlciBvciBub3QgeW91IGFyZSBhd2Fy
ZSBvZiBhbnkgcmVsZXZhbnQgSVBSLg0KDQpUaGUgZHJhZnQgd2lsbCBub3QgYmUgYWRvcHRlZCB1
bnRpbCBhIHJlc3BvbnNlIGhhcyBiZWVuIHJlY2VpdmVkIGZyb20gZWFjaCBhdXRob3IgYW5kIGNv
bnRyaWJ1dG9yLg0KDQpJZiB5b3UgYXJlIG5vdCBsaXN0ZWQgYXMgYW4gYXV0aG9yIG9yIGNvbnRy
aWJ1dG9yLCB0aGVuIHBsZWFzZSBleHBsaWNpdGx5IHJlc3BvbmQgb25seSBpZiB5b3UgYXJlIGF3
YXJlIG9mIGFueSBJUFIgdGhhdCBoYXMgbm90IHlldCBiZWVuIGRpc2Nsb3NlZCBpbiBjb25mb3Jt
YW5jZSB3aXRoIElFVEYgcnVsZXMuDQoNClRoYW5rIHlvdSwNCg0KTWFydGluICYgVGhvbWFzDQps
M3ZwbiBjby1jaGFpcnMNCg0KWzFdIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXp6
aGFuZy1sM3Zwbi1tdnBuLWdsb2JhbC10YWJsZS1tY2FzdC0wNA0KDQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KcGltIG1haWxpbmcgbGlzdA0KcGltQGll
dGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbQ0K


From nobody Thu May 22 22:10:34 2014
Return-Path: <mike.mcbride@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0202F1A0363 for <pim@ietfa.amsl.com>; Thu, 22 May 2014 22:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 84_QNyeBeK6k for <pim@ietfa.amsl.com>; Thu, 22 May 2014 22:10:26 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB1551A0361 for <pim@ietf.org>; Thu, 22 May 2014 22:10:25 -0700 (PDT)
X-AuditID: c6180641-f79df6d000002de0-61-537e86007bd0
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id A6.F4.11744.0068E735; Fri, 23 May 2014 01:19:28 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0174.001; Fri, 23 May 2014 01:10:23 -0400
From: Mike McBride <mike.mcbride@ericsson.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: WGLC: draft-ietf-pim-drlb-03
Thread-Index: Ac92RKTTcHNidFXpQ2G8zQt0EgQ/KQ==
Date: Fri, 23 May 2014 05:10:22 +0000
Message-ID: <6F5149063CE40341BE7953160A93C5A0EE8211@eusaamb109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyuXRPoC5DW12wwftWLYsvD28yOzB6LFny kymAMYrLJiU1J7MstUjfLoEr49jDp0wF3xkrjv3/ytjAeIqxi5GTQ0LAROLBzm3MELaYxIV7 69m6GLk4hASOMkosunmYEcJZzijxettBJpAqNgE9idMLm1lBbBEBRYn2uS1gtrCAqsSzW5eZ IeJaElM/dbJD2HoSh1e/ButlAaq5+Wo7mM0r4C3x8+sXNhCbEWjz91NrwOLMAuISt57MZ4K4 SEBiyZ7zUNeJSrx8/I8VwlaSmPP6GjNEvY7Egt2f2CBsbYllC18zQ8wXlDg58wnLBEbhWUjG zkLSMgtJyywkLQsYWVYxcpQWp5blphsZbmIEhvIxCTbHHYwLPlkeYhTgYFTi4V1wqjZYiDWx rLgy9xCjNAeLkjjvnmtVwUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoY5aPeHjphf5N353m1 xZ7W8Y78QUuPyuYfWLOt7F27RPezf9/2TkhVczBe+frBpBClVSL165hC+F9IJAYn33UoVNv/ Y3GckIRHxNtNjxZJ6isyh5y+/3varJXPeRbZ20/Itgl1W2K25Cn/gddfwmbK6ZreMeBRNDZ6 eerPqQWxv0v3h/4zOPQyQImlOCPRUIu5qDgRAG0jhVtGAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/Wpimt12QnxiiFCeLi8_y2TpMn1I
Subject: [pim] WGLC: draft-ietf-pim-drlb-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 23 May 2014 05:10:33 -0000

Stig and I feel draft-ietf-pim-drlb-03 is ready for WGLC. The authors have =
addressed all comments to date. Today starts a two week WGLC, please speak =
up either way.=20

http://www.ietf.org/id/draft-ietf-pim-drlb-03.txt

thanks,
mike


From nobody Thu May 22 22:20:19 2014
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B25701A036F for <pim@ietfa.amsl.com>; Thu, 22 May 2014 22:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level: 
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 Mxp3beL64BuY for <pim@ietfa.amsl.com>; Thu, 22 May 2014 22:20:14 -0700 (PDT)
Received: from kecgate02.infosys.com (kecgate02.infosys.com [122.98.14.32]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EF921A0371 for <pim@ietf.org>; Thu, 22 May 2014 22:20:12 -0700 (PDT)
X-TM-IMSS-Message-ID: <7a21fda00014ebc7@infosys.com>
Received: from BLRKECHUB11.ad.infosys.com ([10.66.236.43]) by infosys.com ([122.98.14.32]) with ESMTP (TREND IMSS SMTP Service 7.1) id 7a21fda00014ebc7 ; Fri, 23 May 2014 10:45:51 +0530
Received: from BLRKECHUB09.ad.infosys.com (10.66.236.119) by BLRKECHUB11.ad.infosys.com (10.66.236.43) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 23 May 2014 10:47:49 +0530
Received: from BLRKECMBX12.ad.infosys.com ([fe80::a0dd:c35f:79ad:4993]) by Blrkechub09.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Fri, 23 May 2014 10:47:38 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Mike McBride <mike.mcbride@ericsson.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: WGLC: draft-ietf-pim-drlb-03
Thread-Index: Ac92RKTTcHNidFXpQ2G8zQt0EgQ/KQAAWIYy
Date: Fri, 23 May 2014 05:17:38 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED4858ACDB@BLRKECMBX12.ad.infosys.com>
References: <6F5149063CE40341BE7953160A93C5A0EE8211@eusaamb109.ericsson.se>
In-Reply-To: <6F5149063CE40341BE7953160A93C5A0EE8211@eusaamb109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.200.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/QI5haSelZlTYT2uZxtGa4MgEOf4
Subject: Re: [pim] WGLC: draft-ietf-pim-drlb-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 23 May 2014 05:20:18 -0000

Mike, Authors,

       I had sent some questions/suggestions on this draft almost a year =
back.

       Here is the link: http://www.ietf.org/mail-archive/web/pim/current=
/msg02720.html

       I am not sure if I missed the response. I am also not sure if thes=
e has been addresses in the new revision.

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/
________________________________________
From: pim [pim-bounces@ietf.org] on behalf of Mike McBride [mike.mcbride@=
ericsson.com]
Sent: Friday, May 23, 2014 10:40 AM
To: pim@ietf.org
Subject: [pim] WGLC: draft-ietf-pim-drlb-03

Stig and I feel draft-ietf-pim-drlb-03 is ready for WGLC. The authors hav=
e addressed all comments to date. Today starts a two week WGLC, please sp=
eak up either way.

http://www.ietf.org/id/draft-ietf-pim-drlb-03.txt

thanks,
mike

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

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***


From nobody Tue May 27 16:35:55 2014
Return-Path: <sami.biz.email@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C481A07C7 for <pim@ietfa.amsl.com>; Tue, 27 May 2014 16:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.855
X-Spam-Level: **
X-Spam-Status: No, score=2.855 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FRT_BELOW2=2.154, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 cOmidEVDPuRi for <pim@ietfa.amsl.com>; Tue, 27 May 2014 16:35:52 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4474B1A02AF for <pim@ietf.org>; Tue, 27 May 2014 16:35:52 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id a1so10287382wgh.27 for <pim@ietf.org>; Tue, 27 May 2014 16:35:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type; bh=KNFvbOjiFFJ48IpAjcTtz0Jnz+N2VV7eftDqxg/E07M=; b=JJR0SFSLD8cz26A9ppqOlkn83ALQgFkAiNJsg+0V0MtSEdU3PiwqMVeI+mitXj09CU 79VNL+0ZoGfWs6/prXVnPnLyDMcK3bMZhLzYdgnVGCgJ4AS+H8zgxIMVgPviTcLfjdaj VapZ70XyWCw3FFSCXbSARnBzSUO8ns5NX+kACFL3C5fSZmFYB/4+FtgFQy33pAGKh0GI ynEEyEIKrZdDyJ/PgaL4tGih47vLcGqg7xQq87MRYOrvkbF7lDgQ9BIKvbwcb/idqjds 1MfqQ4FARb2l+1i+caRyvUf749xtXiLG7rvQtFK169F5clhVmtZwMhJoL1rY0YnlIF5i p7Jw==
X-Received: by 10.180.211.243 with SMTP id nf19mr42260202wic.58.1401233747702;  Tue, 27 May 2014 16:35:47 -0700 (PDT)
Received: from [192.168.1.3] ([178.253.49.188]) by mx.google.com with ESMTPSA id g10sm38562085wjs.33.2014.05.27.16.35.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 May 2014 16:35:46 -0700 (PDT)
Message-ID: <53852E73.9000507@gmail.com>
Date: Wed, 28 May 2014 04:01:47 +0330
From: saeed sami <sami.biz.email@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: pim@ietf.org, pim-chairs@tools.ietf.org
Content-Type: multipart/alternative; boundary="------------060902070309050001030203"
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/1M00R92JJgEcz5hUHBmKvFTTdDY
Subject: [pim]  draft-sami-pim-ng-02 PIM-NG advantages (part 1)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 27 May 2014 23:35:54 -0000

This is a multi-part message in MIME format.
--------------060902070309050001030203
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello.

This email might be a little too long but it is worth reading since it 
is about some of the key advantages of the new proposed protocol, and I 
hope that it will be read by WG experts.  It is related to some of the 
advantages of PIM-NG the new proposed PIM protocol. The draft can be 
find at:

http://tools.ietf.org/html/draft-sami-pim-ng-02

since It was not possible to send the email at once I will have to send 
it to the mailing list  in separate parts , and this is part 1 of the 
series.

Some of the key advantages of PIM-NG that can make it a potential 
candidate for adoption by the WG are explained bellow:

1-Different concepts of PIM-NG with regards to RP discovery and other 
processes are designed in a way to provide an easy to implement (to some 
extents), automatic or intelligent routing protocol to some extents. 
This is achieved by introducing new processes and packet types which 
allow PIM-NG components such as C-RP's, C-MAPPER's and ... to converge 
and fin each other automatically and in the lowest time interval.

2-the definition and role of existing RP'(S) and BSR'(s) weren't clear 
at least to my eyes which guided me towards a little bit different 
definition with regards to how the exiting components of a PIM-NG 
multicast network are introduced to the PIM-NG population.

3-A PIM-NG MAPPER which can be considered as a BSR too, has a more vital 
role in PIM-NG which makes it possible to follow a hierarchical design 
pattern.

4-PIM-NG uses a new source register process which makes the size of 
register packets smaller due to the fact that there will be no need for 
data packet to be sent alongside the register message.  This will reduce 
the bandwidth and resource consumption since no data packet is sent in a 
register message.

5-The source discovery method used by PIM-SM seemed a little 
un-optimized in parts mainly related to a last hop router joining the 
RPT rooted at the RP first and then switch to SPT. This process is not 
necessary and is network resource consuming. So a new process is defined 
in PIM-NG which eliminates the need for the (*, G) RPT tree to form 
first. The new source discovery method puts PIM-NG one cycle a head of 
PIM-SM in finding and communicating with a source.

End of part 1.
-- 
sincerely yours
MR.SAEED SAMI

--------------060902070309050001030203
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p class="MsoNormal" style="direction:ltr">Hello.</p>
    <p class="MsoNormal" style="direction:ltr">This
      email might be a little too long but it is worth reading since it
      is about some of the key advantages of the new proposed protocol,
      and I hope that it
      will be read by WG experts.&nbsp; It is
      related to some of the advantages of PIM-NG the new proposed PIM
      protocol. The draft
      can be find at: </p>
    <p class="MsoNormal" style="direction:ltr">&nbsp;<a
        href="http://tools.ietf.org/html/draft-sami-pim-ng-02">http://tools.ietf.org/html/draft-sami-pim-ng-02</a>
      &nbsp;</p>
    <p class="MsoNormal" style="direction:ltr">since
      It was not possible to send the email at once I will have to send
      it to the
      mailing list &nbsp;in separate parts , and
      this is part 1 of the series.</p>
    <p class="MsoNormal" style="direction:ltr">Some
      of the key advantages of PIM-NG that can make it a potential
      candidate for
      adoption by the WG are explained bellow:</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">1-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>Different concepts of
      PIM-NG with regards to RP discovery and other processes are
      designed in a way
      to provide an easy to implement (to some extents), automatic or
      intelligent routing
      protocol to some extents. This is achieved by introducing new
      processes and packet
      types which allow PIM-NG components such as C-RP's, C-MAPPER's and
      &#8230; to
      converge and fin each other automatically and in the lowest time
      interval.</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">2-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>the definition and role of
      existing RP'(S) and BSR'(s) weren't clear at least to my eyes
      which guided me
      towards a little bit different definition with regards to how the
      exiting
      components of a PIM-NG multicast network are introduced to the
      PIM-NG
      population.</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">3-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>A PIM-NG MAPPER which can
      be considered as a BSR too, has a more vital role in PIM-NG which
      makes it
      possible to follow a hierarchical design pattern.</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">4-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>PIM-NG uses a new source
      register process which makes the size of register packets smaller
      due to the
      fact that there will be no need for data packet to be sent
      alongside the register
      message.&nbsp; This will reduce the bandwidth
      and resource consumption since no data packet is sent in a
      register message.</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">5-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>The source discovery method
      used by PIM-SM seemed a little un-optimized in parts mainly
      related to a last
      hop router joining the RPT rooted at the RP first and then switch
      to SPT. This
      process is not necessary and is network resource consuming. So a
      new process is
      defined in PIM-NG which eliminates the need for the (*, G) RPT
      tree to form
      first. The new source discovery method puts PIM-NG one cycle a
      head of PIM-SM
      in finding and communicating with a source.</p>
    <div>End of part 1.&nbsp;</div>
    -- <br>
    sincerely yours<br>
    MR.SAEED SAMI
  </body>
</html>

--------------060902070309050001030203--


From nobody Wed May 28 11:28:48 2014
Return-Path: <hou@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8DF1A049E for <pim@ietfa.amsl.com>; Wed, 28 May 2014 11:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.452
X-Spam-Level: 
X-Spam-Status: No, score=-12.452 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 RAB-RtV_pFvD for <pim@ietfa.amsl.com>; Wed, 28 May 2014 11:28:39 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DADF1A04A8 for <pim@ietf.org>; Wed, 28 May 2014 11:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19674; q=dns/txt; s=iport; t=1401301715; x=1402511315; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=m/z6O7Ew4NKQXTHWUFZDarMfPqDbduG6D40u8kwCjic=; b=jJxgRjGFRskQYM78iDkJGpa+pGwTQXCfnZIBd3BvjxO61CXdGTDtyPJ0 ClpAb1z+Xy6RFy9sWstcRhQuO7QFv5QdR2lj0aBOoC6aoj/zOpDKBzDaH /D1jMLuKX6PknZq25YZ067DdNmBYsyM4eU/g2MI9YfH5HcYstPWi5BwOe A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkMFAI8phlOtJA2F/2dsb2JhbABZgwdSWIJruAGHOgEZdRZ0giUBAQEEAQEBCxURMQkdAQgRBAEBAwImAgQlCxUICAEBBAESCYg5DbJwpCMXgSqMVwEBNCIGgm+BSwSFRJQxgT2CdI52gzhsgQo5
X-IronPort-AV: E=Sophos;i="4.98,929,1392163200"; d="scan'208";a="328393856"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-1.cisco.com with ESMTP; 28 May 2014 18:28:33 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s4SISX19030479 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 28 May 2014 18:28:33 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.164]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Wed, 28 May 2014 13:28:33 -0500
From: "Heidi Ou (hou)" <hou@cisco.com>
To: Bharat Joshi <bharat_joshi@infosys.com>, Mike McBride <mike.mcbride@ericsson.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] WGLC: draft-ietf-pim-drlb-03
Thread-Index: Ac92RKTTcHNidFXpQ2G8zQt0EgQ/KQAAWIYyARL1d4A=
Date: Wed, 28 May 2014 18:28:32 +0000
Message-ID: <CFAB6B69.9D39A%hou@cisco.com>
In-Reply-To: <35347FBF2796F94E936EE76C0E6047ED4858ACDB@BLRKECMBX12.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.154.210.10]
Content-Type: text/plain; charset="utf-8"
Content-ID: <213DC7CD2F0E1B43A59A9E57D6BFC4B5@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/eh-yhLIa8SRcCzP0US90MkThQx8
Subject: Re: [pim] WGLC: draft-ietf-pim-drlb-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 May 2014 18:28:44 -0000

SGkgQmhhcmF0LA0KDQpUaGFua3MgZm9yIHlvdXIgY29tbWVudHMsIHNvcnJ5IHRvIHJlcGx5IHRo
aXMgbGF0ZSwgYnV0DQp3ZSBoYXZlIG1hZGUgcXVpdGUgYSBmZXcgY2hhbmdlcyBzaW5jZSAtMDIt
IChsYXRlc3QgaXMgLTAzLSksDQplc3BlY2lhbGx5IGluIHNlY3Rpb24gNi4yIGFuZCA2LjMuDQoN
ClBsZWFzZSBmaW5kIHJlcGx5IGlubGluZSwgc2VhcmNoIGZvciBbaGVpZGldDQoNCg0KDQpGcm9t
OiBCaGFyYXQgSm9zaGkNClNlbnQ6IEZyaWRheSwgSnVuZSAyOCwgMjAxMyA0OjA5IFBNDQpUbzog
cGltIGF0IGlldGYub3JnDQpTdWJqZWN0OiBGZXcgcXVlc3Rpb25zL3N1Z2dlc3Rpb24gb24gRFIg
TG9hZCBCYWxhbmNpbmcgZHJhZnQNCg0KSGksDQoNCiAgICAgICBJIGp1c3QgcmVhZCB0aHJvdWdo
IHRoZSBEUiBMb2FkIEJhbGFuY2luZyBkcmFmdC4gSSBoYXZlIGZldw0KcXVlc3Rpb25zL3N1Z2dl
c3Rpb24gYmVsb3cuDQoNClJlZ2FyZHMsDQpCaGFyYXQNCg0K4oKsIEluIEFic3RyYWN0LCBzL2Fz
IGFuIEV0aGVybmV0L2FzIEV0aGVybmV0L2cuIFRoaXMgc2VlbXMgdG8gYmUgYXQgY291cGxlDQpv
ZiBwbGFjZXMuDQoNCg0KW2hlaWRpXSBPaw0KDQpbaGVpZGldIEkgd2lsbCB0cnkgdG8gZml4IHNv
bWUgb2YgdGhlIG9idmlvdXMgZXJyb3JzIGFuZCBmb2xsb3cgdXAgd2l0aA0KW2hlaWRpXSBjaGFp
cnMgdG8gc2VlIGhvdyB3ZSBjYW4gZ2V0IHN1Y2ggYSByZXZpZXcgZG9uZS4NCltoZWlkaV0gSSBy
ZW1lbWJlciB3ZSBoYXZlIGEgcmV2aWV3IHNwZWNpZmljYWxseSBmb3IgdGhlIHByb3BlciBhbmQN
CltoZWlkaV0gYWNjdXJhdGUgdXNlIG9mIHRoZSBFbmdsaXNoIGxhbmd1YWdlIGluIGFuIEktRC4N
Cg0KDQoNCuKCrCBBcmUgJ2ZpcnN0IGhvcCBuZXR3b3JrJyBvciAnbGFzdCBob3AgTEFOJyBhIHdl
bGwga25vd24gdGVybT8gV2lsbCBpdCBiZQ0KZWFzeSBmb3IgcGVvcGxlIHRvIHVuZGVyc3RhbmQg
dGhhdCB0aGlzIGlzIGJlaW5nIHRhbGtlZCBmcm9tIG11bHRpY2FzdA0Kc291cmNlIHBlcnNwZWN0
aXZlPyBDYW4gd2UgY2FsbCB0aGVtIGRpcmVjdGx5IGNvbm5lY3RlZCBMQU4gaW4gYm90aCB0aGUN
CmNhc2VzPw0KDQpbaGVpZGldIFRoZXkgYXJlIHdlbGwta25vd24uICBHb29nbGluZyDCs3BpbSBm
aXJzdCBob3DCsiB3aWxsIGdlbmVyYXRlDQpyZWZlcmVuY2UgZnJvbSBzZXZlcmFsIGRpZmZlcmVu
dCBzb3VyY2VzLg0KDQoNCg0K4oKsIEluIEFic3RyYWN0LCBzL2lzIG9wZXJhdGVkIGluIFBJTSBT
TS9pcyBvcGVyYXRpbmcgaW4gUElNIFNNL2cuIFRoaXMgaXMNCmF0IGxlYXN0IGF0IHR3byBwbGFj
ZXMuDQoNCltoZWlkaV0gZG9uZQ0KDQoNCuKCrCBJbiBBYnN0cmFjdCwgaW4gZm9sbG93aW5nIHNl
bnRlbmNlOg0KDQpPbiB0aGUgbGFzdCBob3AgbmV0d29yaywgdGhlIFBJTSBEUiBpcyByZXNwb25z
aWJsZSBmb3IgdHJhY2tpbmcgbG9jYWwNCm11bHRpY2FzdCBsaXN0ZW5lcnMgYW5kIGZvcndhcmRp
bmcgdHJhZmZpYyB0byB0aGVzZSBsaXN0ZW5lcnMgaWYgdGhlIGdyb3VwDQppcyBvcGVyYXRlZCBp
biBQSU0gU00vU1NNL0RNLg0KDQpTaG91bGQgd2UgbWVudGlvbmluZyBCSURJUi1QSU0gYXMgd2Vs
bCBpbiB0aGlzIGxpc3Q/IE9yIHN1Y2ggYSBncm91cCBpcw0KdHJlYXRlZCBkaWZmZXJlbnRseT8N
Cg0KDQpbaGVpZGldIFRoZSBjb25jZXB0IG9mIFBJTS1EUiBpcyBub3QgcmVsZXZhbnQgZm9yIEJp
ZGlyLVBJTS4gIEluDQpbaGVpZGldIEJpZGlyLVBJTSwgaXQgaXMgdGhlIERGIHRoYXQgaGFuZGxl
cyBmb3J3YXJkaW5nLg0KDQoNCg0K4oKsIEluIEFic3RyYWN0LCBzL2NhbiBiZSBkaXN0cmlidXRl
ZCB0byBhbmQgaGFuZGxlZCBhbW9uZyB0aGVzZS9jYW4gYmUNCmRpc3RyaWJ1dGVkIGFtb25nIHRo
ZXNlLw0KDQpbaGVpZGldIGRvbmUNCg0KDQrigqwgSW4gR0RSIGRlZmluaXRpb24sIGl0IHRhbGtz
IGFib3V0IHRoYXQgR0RSIGlzIHJlc3BvbnNpYmxlIGZvciBhIGdyb3VwLg0KRG9lcyB0aGlzIG1l
YW4gdGhhdCBhIHNpbmdsZSBHRFIgd2lsbCBiZSByZXNwb25zaWJsZSBmb3IgYWxsIGNoYW5uZWxz
DQooUyxHKSBmb3IgYSBnaXZlbiBncm91cCBidXQgZGlmZmVyZW50IHNvdXJjZXM/DQoNCltoZWlk
aV0gV2hpY2ggZmxvdywgaS5lLiwgKFMsRyksIGEgR0RSIGlzIHJlc3BvbnNpYmxlIGZvciBkZXBl
bmRzIG9uIHRoZQ0KW2hlaWRpXSBoYXNoIGZ1bmN0aW9uLg0KDQoNCg0K4oKsIHMvcHJvY2VzcyBy
ZWNlaXZlZCBuZXcgUElNIEhlbGxvL3Byb2Nlc3MgbmV3IFBJTSBIZWxsby8NCg0K4oKsIEluIElu
dHJvZHVjdGlvbiwgaW4gZm9sbG93aW5nIHNlbnRlbmNlOg0KDQpBY2NvcmRpbmcgdG8gW1JGQzQ2
MDFdLCBSMSB3aWxsIGJlIHJlc3BvbnNpYmxlIGZvciBmb3J3YXJkaW5nIHRvIHRoZSBsYXN0DQpo
b3AgTEFOLg0KDQogICAgICAgQ2FuIHdlIHJlcGxhY2UgdGhpcyBzZW50ZW5jZSBieSBzb21ldGhp
bmcgc2ltaWxhciB0byBhIHNlbnRlbmNlDQpmcm9tIFJGQyA0NjAxLCBzZWN0aW9uIDYuMS4xIHBv
aW50IDIuIFRoZSBzZW50ZW5jZSBpcyBhcyBmb2xsb3dzOg0KDQpUaGUgZGVzaWduYXRlZCByb3V0
ZXIgb24gYSBMQU4gaXMgKGluIHRoZSBhYnNlbmNlIG9mIGFzc2VydHMpIHJlc3BvbnNpYmxlDQpm
b3IgZm9yd2FyZGluZyB0cmFmZmljIHRvIHRoYXQgTEFOIG9uIGJlaGFsZiBvZiBhbnkgbG9jYWwg
bWVtYmVycy4NCg0KDQpbaGVpZGldIHN1cmUuDQoNCg0K4oKsIFRoZXJlIG1heSBiZSBhIG1peCBv
ZiBsb2NhbCBob3N0cyBhcyB3ZWxsIGFzIGRvd25zdHJlYW0gcm91dGVycyBpbiBhDQpuZXR3b3Jr
IHNjZW5hcmlvLiBEbyB3ZSBzdGlsbCBjYWxsIHRoaXMgdGhlIGxhc3QgaG9wIExBTj8gSSBndWVz
cyB5ZXMgYW5kDQpJIHRoaW5rIHRoZXJlIGNhbiBzdGlsbCBiZSBHRFIgY2FuZGlkYXRlIGFuZCB0
aGlzIGRyYWZ0IGNhbiBhcHBseS4gUmlnaHQ/DQpJIHRoaW5rIHRoaXMgaXMgbm90IGNvbWluZyBv
dXQgd2VsbCBpbiB0aGUgZHJhZnQuIFNvIHBsZWFzZSBhZGQvdXBkYXRlDQpzb21lIHRleHQgdG8g
cmVmbGVjdCB0aGlzLg0KDQpbaGVpZGldIFRoZSBkcmFmdCBzaG91bGQgc3RpbGwgYXBwbHkgaW4g
dGhlIHNjZW5hcmlvIGRlc2NyaWJlZC4NCg0K4oKsIEluIHNlY3Rpb24gMywgSSBkaWQgbm90IGdl
dCB3aGF0ICdsb2FkIGJhbGFuY2luZycgYXJlIHdlIHRhbGtpbmcgYWJvdXQNCmluIGNhc2Ugb2Yg
J2ZpcnN0IGhvcCByb3V0ZXJzJz8NCg0KW2hlaWRpXSBJdCBpcyByZWZlcnJpbmcgdG8gdGhlIGNv
bW1vbiBpbXBsZW1lbnRhdGlvbiB0aGF0IHdoZW4gYSBkb3duc3RyZWFtDQpbaGVpZGldIHJvdXRl
ciBoYXMgbXVsdGlwbGUgdXBzdHJlYW0gbmVpZ2hib3JzIHRoYXQgYXJlIGVxdWFsIGNvc3QgYXMN
CltoZWlkaV0gZGV0ZXJtaW5lZCBieSBJR1AsDQpbaGVpZGldIGl0IHdpbGwgwrNsb2FkIGJhbGFu
Y2XCsiB0aGUgam9pbnMgd2hlbiBjaG9vc2luZyBhbiB1cHN0cmVhbQ0KW2hlaWRpXSBuZWlnaGJv
ci4NCg0KDQrigqwgSW4gc2VjdGlvbiAzLCBJIGFsc28gZGlkIG5vdCB1bmRlcnN0YW5kIGhvdyBF
Q01QIGhlbHBzIGluIHRoaXMgbG9hZA0KYmFsYW5jaW5nLiBJZiB0aGVyZSBhcmUgbXVsdGlwbGUg
cm91dGVycyBvbiBhIExBTiBpbiB3aGljaCB0aGUgc291cmNlIGFsc28NCnNpdHMsIGFzIHBlciBQ
SU0sIGl0cyB0aGUgRFIgd2hvIGlzIHRvIHNlbmQgdGhlIHJlZ2lzdGVyIG1lc3NhZ2VzIHRvIHRo
ZQ0KUlAuIFNvIEkgYW0gbm90IHN1cmUgaG93IEVDTVAgaGVscHMgaGVyZSBpbiBtYWtpbmcgb3Ro
ZXIgcm91dGVyIG9uIHRoaXMNCkxBTiB0byBkbyB0aGlzIGluc3RlYWQgb2YgdGhlIERSPw0KDQpb
aGVpZGldIFllcyBpdCBpcyB0aGUgRFIgdGhhdCBzZW5kcyB0aGUgcmVnaXN0ZXJzLiAgQnV0IHRo
ZSBwYWNrZXRzIGFyZQ0KW2hlaWRpXSBtb3N0bHkgZm9yd2FyZGVkIG5hdGl2ZWx5DQpbaGVpZGld
IGRvd24gdGhlIHNvdXJjZSB0cmVlcyBlc3RhYmxpc2hlZCBieSAoUyxHKSBqb2lucyBmcm9tIGRv
d25zdHJlYW0NCltoZWlkaV0gcm91dGVycy4NCg0KDQoNCuKCrCBBcyBwZXIgUkZDIDQ2MDEsIFBJ
TSBEUiBpcyBlbGVjdGVkIGZvciBhbnkgdHlwZSBvZiBuZXR3b3JrcyBzbyB0aGVyZSBpcw0Kbm8g
bmVlZCB0byBtZW50aW9uIHRoYXQgUElNIERSIGVsZWN0aW9uIGlzIGRvbmUgaW4gYSBtdWx0aS1h
Y2Nlc3MgbmV0d29yay4NCg0KW2hlaWRpXSBJIGFtIG1pc3NpbmcgdGhlIHlvdXIgcG9pbnQgaGVy
ZS4NCg0KDQoNCuKCrCBJbiBzZWN0aW9uIDQsIGluIHNlbnRlbmNlICJUaGUgUElNIERSIGlzIHJl
c3BvbnNpYmxlIGZvciBzZW5kaW5nDQpKb2luL1BydW5lIG1lc3NhZ2VzIHRvIHRoZSBSUCBvciBz
b3VyY2UuIiwgSSB0aGluayB3ZSBzaG91bGQgbWVudGlvbiB0aGF0DQp0aGlzIGlzIGRvbmUgZm9y
IHRoZSBsb2NhbCBob3N0J3Mgam9pbi9sZWF2ZS4NCg0KW2hlaWRpXSBUaGF0IHdvdWxkIGJlIHJl
ZHVuZGFudC4gSWYgaXQgaXMgbm90IGZvciBsb2NhbCBob3N0cywgdGhlbiBpdA0KW2hlaWRpXSBk
b2VzbsK5dCBtYXR0ZXIgd2hldGhlciB0aGUgcm91dGVyIGlzIGEgRFIgb3Igbm90IG9uIHRoZSBp
bnRlcmZhY2UNCltoZWlkaV0gZnJvbSB3aGljaCBhIFBJTSBKb2luL1BydW5lIGlzIHJlY2VpdmVk
Lg0KDQoNCg0K4oKsIEluIHNlY3Rpb24gNCwgcGFyYSAxLCBJIHRoaW5rIGl0IHNob3VsZCBiZSBl
bm91Z2ggaWYgdGhlIHRleHQgc3VnZ2VzdA0KdGhhdCBQSU0gRFIgZWxlY3Rpb24gaXMgZG9uZSBh
cyBwZXIgUkZDIDQ2MDEgaW5zdGVhZCBvZiBkZXNjcmliaW5nIHRoZQ0KYWxnb3JpdGhtIGhlcmUu
DQoNCltoZWlkaV0gV2Ugd2lsbCBrZWVwIHRoZSB0ZXh0LiBBbm90aGVyIHJldmlld2VyIG1pZ2h0
IHdpc2ggdG8gaGF2ZSB0aGUNCltoZWlkaV0gYWRkaXRpb25hbCBkZXNjcmlwdGlvbi4NCg0KDQoN
Cg0K4oKsIHMvcm91dGVycyBzdXBwb3J0IHRoaXMgc3BlY2lmaWNhdGlvbi9yb3V0ZXJzIHdoaWNo
IHN1cHBvcnQgdGhpcw0KU3BlY2lmaWNhdGlvbi8NCg0KW2hlaWRpXSBvay4NCg0K4oKsIEluIHNl
Y3Rpb24gNCwgY2FuIHdlIHJld29yZCB0aGUgZm9sbG93aW5nIHNlbnRlbmNlOg0KDQpMYXN0IGhv
cCByb3V0ZXJzIHdobyBhcmUgd2l0aCB0aGUgbmV3IExCQyBUTFYgYW5kIHdpdGggdGhlIHNhbWUg
RFINCnByaW9yaXR5IGFzIHRoZSBQSU0gRFIgYXJlIEdEUiBDYW5kaWRhdGVzLg0KDQp0bw0KDQpM
YXN0IGhvcCByb3V0ZXJzIHdoaWNoIHN1cHBvcnRzIHRoZSAnTG9hZCBCYWxhbmNpbmcgQ2FwYWJp
bGl0eScgUElNIGhlbGxvDQpvcHRpb24gYW5kIHVzZXMgdGhlIHNhbWUgRFIgcHJpb3JpdHkgYXMg
dGhlIFBJTSBEUiwgYXJlIGNvbnNpZGVyZWQgdG8gYmUNCkdEUiBDYW5kaWRhdGVzLg0KDQpbaGVp
ZGldIG9rDQoNCuKCrCBJbiBzZWN0aW9uIDQsIGxhc3QgcGFyYSwgY2FuIHdlIGNsZWFybHkgbWVu
dGlvbiB0aGF0IHdlIGFyZSByZWZlcnJpbmcgdG8NCmdyb3VwcyBqb2luZWQgYnkgbG9jYWwgbWVt
YmVycyBvbmx5Lg0KDQpbaGVpZGldIEFzIG1lbnRpb25lZCBlYXJseSwgVGhlIGNvbnRleHQgb2Yg
dGhpcyBkcmFmdCBpcyBmb3IgZGlyZWN0bHkNCltoZWlkaV0gYXR0YWNoZWQgaG9zdC4gV2UgYXJl
IG5vdCBtb2RpZnlpbmcgYW55IGJlaGF2aW9yIG9mIGEgUElNIHJvdXRlcg0KW2hlaWRpXSB3aGVu
IGl0IHJlY2VpdmVzIGEgUElNIEpvaW4vUHJ1bmUuDQoNCg0K4oKsIEkgdGhpbmsgc2VjdGlvbiA0
LjIgc2hvdWxkIGJlIGRpdmlkZWQgaW50byB0d28sIG9uZSB0aGF0IGRlZmluZWQgaGFzaA0KbWFz
ayBhbmQgYW5vdGhlciB0aGF0IGRlZmluZXMgdGhlIGhhc2ggZnVuY3Rpb24uDQoNCltoZWlkaV0g
aXQgaXMgbm90IGEgbGFyZ2UgcGFyYWdyYXBoLCB3ZSB3aWxsIGtlZXAgaXQgYXMgaXMuDQoNCuKC
rCBBcGFydCBmcm9tIHRoZSBoYXNoIHZhbHVlL2Z1bmN0aW9uLCBjYW5ub3QgYW4gYWRtaW5pc3Ry
YXRvciBjb25maWd1cmUNCnRoZSBtYXBwaW5nIHN0YXRpY2FsbHk/IFRoaXMgd2F5LCBhbiBhZG1p
bmlzdHJhdG9yIHdpbGwgaGF2ZSBtb3JlIGNvbnRyb2wNCm9uIHdoaWNoIGNoYW5uZWwgaXMgcmVn
aXN0ZXJlZCBieSB3aGljaCBEUiBhbmQgYWxzbywgaGUgd29uJ3QgbmVlZCB0aGVzZQ0KbmV3IGhl
bGxvIG9wdGlvbnMuIEkgYWdyZWUgdGhhdCBzdWNoIGEgdGhpbmcgd2lsbCB3b3JrIG9ubHkgaWYg
YWxsIHZlbmRvcnMNCnByb3ZpZGUgc3VjaCBhIG1lYW4gdG8gdGhlIGFkbWluaXN0cmF0b3JzLg0K
DQpbaGVpZGldIENvcnJlY3QuIFdlIGFyZSB0cnlpbmcgdG8gcmVkdWNlIHVubmVjZXNzYXJ5IGNv
bmZpZ3VyYXRpb24sIGFuZA0KW2hlaWRpXSByZWR1Y2UgdGhlIHBvc3NpYmlsaXR5IG9mIGluY29u
c2lzdGVuY3kuDQoNCg0KDQrigqwgSW4gc2VjdGlvbiA0LjMsIGl0cyBub3QgY2xlYXIgd2hhdCB3
aWxsIGJlIHRoZSBjb250ZW50cyBvZiBmaXJzdCBQSU0NCmhlbGxvIG1lc3NhZ2Ugb2YgYSByb3V0
ZXIgY29taW5nIHVwPyBXaWxsIGl0IGNvbnRhaW4gTEIgR0RSIG9wdGlvbiBvciBub3Q/DQpBdCB0
aGF0IHRpbWUsIGl0IG1heSBub3Qga25vdyB3aGV0aGVyIGl0cyBhIERSIG9yIG5vdC4gQWN0dWFs
bHksIGl0IHdpbGwNCmFzc3VtZSB0aGF0IGl0cyB0aGUgRFIgdW50aWwgaXQgcmVjZWl2ZXMgYSBo
ZWxsbyBtZXNzYWdlIGZyb20gYSBoaWdoZXIgRFINCnByaW9yaXR5IHJvdXRlci4NCg0KDQpbaGVp
ZGldIEl0IGRlcGVuZHMgb24gdGhlIGltcGxlbWVudGF0aW9uwrlzIGNob2ljZSB3aGV0aGVyIGl0
IGNvbnNpZGVycw0KW2hlaWRpXSBpdHNlbGYgYXMgYSBEUiB3aGVuIHRoZSBpbnRlcmZhY2UgY29t
ZXMgdXAuDQpbaGVpZGldIFRoZSBkcmFmdCBkb2VzbsK5dCBpbnRlbmQgdG8gZGljdGF0ZSB0aGF0
IGNob2ljZS4gSVQganVzdCBzcGVjaWZpZXMNCltoZWlkaV0gd2hhdCB0byBzZW5kLg0KDQoNCg0K
4oKsIEluIHNlY3Rpb24gNS4yLCBzaG91bGQgd2UgYmUgdXNpbmcgZW5jb2RlZCBmb3JtYXQgZGVm
aW5lZCBpbiBSRkMgNDYwMQ0KZm9yIEdEUiBhZGRyZXNzZXMgb3IgdXNpbmcgaXQgaW4gbmF0aXZl
IGZvcm1hdCBpcyBmaW5lPw0KDQpbaGVpZGldIFRoZSBlbmNvZGVkIGZvcm1hdCBkb2VzbsK5dCBo
YW5kbGUgbm9uLWNvbnRpZ3VvdXMgbWFzay4NCg0KDQoNCuKCrCBXaGF0IGlzIHRoZSBpZGVhIG9m
IHNlbmRpbmcgdGhlIG1hc2tzIGZyb20gUElNIERSIHRvIG90aGVyIHJvdXRlcnM/IFdoeQ0KY2Fu
bm90IHRoZXkgYmUgY29uZmlndXJlZCBpbiBhbGwgdGhlIHJvdXRlcnM/DQpbaGVpZGldIHllcywg
YnV0IHdlIHdhbnQgdG8gdXNlIHRoZSBwcm90b2NvbCB0byBoYW5kbGUgdGhpcyBhdXRvbWF0aWNh
bGx5LA0KYW5kIGNvbnNpc3RlbnRseS4NCg0KDQrigqwgcy9XaGVuIGFuIElHTVAgam9pbiBpcyBy
ZWNlaXZlZC9XaGVuIGFuIElHTVAvTUxEIGpvaW4gaXMgcmVjZWl2ZWQvDQrigqwgcy9hIG5laWdo
Ym9yIEhlbGxvIHdpdGgvYSBQSU0gSGVsbG8gd2l0aC8NCg0KW2hlaWRpXSBvaw0KDQoNCuKCrCBX
aGF0IGhhcHBlbnMgd2hlbiBhIFBJTSByb3V0ZXIgc3VwcG9ydGluZyB0aGlzIG5ldyBvcHRpb25z
IHRpbWVzIG91dCBpbg0KUElNIERSIHJvdXRlcj8NCg0KW2hlaWRpXSBUaGVuIGFub3RoZXIgcm91
dGVyIHdpbGwgYmVjb21lIHRoZSBEUiBhbmQgdGFrZSBvdmVyIHRoZQ0KW2hlaWRpXSByZXNwb25z
aWJpbGl0eS4NCg0KDQoNCg0K4oKsIERvZXMgUElNIERSIGluc2VydCBpdHMgb3duIGFkZHJlc3Mg
YXMgd2VsbCBpbiB0aGUgbmVpZ2hib3IncyBhZGRyZXNzDQppbnRvIHRoZSBMQkdSRCBUTFYgbGlz
dD8NCg0KW2hlaWRpXSB5ZXMuDQoNCuKCrCBJbiBzZWN0aW9uIDYuMiwgZmlyc3QgcGFyYSB0YWxr
cyBhYm91dCByb3V0ZXIgUjEuIElzIGl0IHJlZmVycmluZyB0bw0KZmlndXJlIDE/DQoNCltoZWlk
aV0gSXQncyBhY3R1YWxseSBqdXN0IHJlZmVycmluZyB0byBQSU0gRFIuIEkgd2lsbCByZW1vdmUg
aXQsDQpbaGVpZGldIGp1c3Qgc2F5aW5nICJQSU0gRFIiLg0KDQrigqwgSW4gc2VjdGlvbiA2LjIs
IHNob3VsZCBub3Qgd2UgbWVudGlvbiB3aGF0IGEgR0RSIGNhbmRpZGF0ZSBkb2VzIHdoZW4gYQ0K
UElNIGhlbGxvIGZyb20gUElNIERSIGlzIHJlY2VpdmVkPyBJIHRoaW5rIGZldyBsYXN0IHBhcmFz
IGF0IHRoZSBlbmQgb2YNCnRoaXMgc2VjdGlvbiBzaG91bGQgYmUgaW4gdGhlIGZyb250LiBQbGVh
c2UgY2hlY2suDQoNCltoZWlkaV0gQ291bGQgeW91IHBsZWFzZSBiZSBtb3JlIHNwZWNpZmljIGFi
b3V0IHdoYXQgaXMgbWlzc2luZyBhbmQNCltoZWlkaV0gc3VnZ2VzdCB0ZXh0Pw0KDQoNCuKCrCBz
L2Zyb20gYSBub24tRFIgUElNIHJvdXRlci9mcm9tIGEgUElNIHJvdXRlciB3aGljaCBpcyBub3Qg
RFIvDQoNCltoZWlkaV0gb2sNCg0K4oKsIEluIHNlY3Rpb24gNi4yLCBpdHMgbm90IGNsZWFyIGlm
IHRoZSBoYXNoIGlzIGNhbGN1bGF0ZWQgb25seSBmb3IgJ1gnIG9yDQpmb3IgYWxsIHRoZSBHRFIg
YXZhaWxhYmxlIGluIHRoZSBsaXN0LiBJIHRoaW5rIGl0IG5lZWRzIHRvIGJlIGNhbGN1bGF0ZWQN
CmZvciBhbGwgb2YgdGhlbSBhbmQgdGhlbiBpZiBoYXNoIGlzIGhpZ2hlc3QgZm9yICdYJywgaXRz
IHNlbGVjdGVkLA0Kb3RoZXJ3aXNlIG5vdC4NCg0KW2hlaWRpXSBJbiB0aGUgbGF0ZXN0IHZlcnNp
b24sIC0wMy0sIHRoZSBoYXNoIHZhbHVlIGlzIGNvbXB1dGVkIGZvciBYDQpbaGVpZGldIG9ubHku
IElmIHRoZSBoYXNoIHZhbHVlIG1hdGNoZXMgdGhlIG9yZGluYWwgbnVtYmVyIGFzc2lnbmVkIHRv
IFgsIFgNCltoZWlkaV0gd2lsbCBiZSB0aGUgR0RSLg0KDQrigqwgSW4gc2VjdGlvbiA2LjMsIGlu
IGNhc2Ugb2YgUElNIGFzc2VydCwgc2hvdWxkIG5vdCB3ZSBvdmVycmlkZSB0aGUNCmV4aXN0aW5n
IEFzc2VydCBhbGdvcml0aG0gY29tcGxldGVseSBhbmQgc3VnZ2VzdCB0aGF0IHRoZSB3aW5uZXIg
c2hvdWxkIGJlDQpzZWxlY3RlZCBiYXNlZCBvbiB0aGUgY3VycmVudGx5IHNlbGVjdGVkIEdEUj8N
Cg0KW2hlaWRpXSBDb3VsZCB5b3UgcGxlYXNlIGVsYWJvcmF0ZSB0aGUgcmVhc29ucyB3aHkgNi4z
IGlzIGluc3VmZmljaWVudCBpbg0KW2hlaWRpXSB0aGlzIGNhc2U/DQoNCg0K4oKsIFdoYXQgaGFw
cGVucyB3aGVuIGEgbmV3IHJvdXRlciBjb21lcyB1cCB3aGljaCBiZWNvbWVzIHRoZSBEUiBidXQg
ZG9lcw0Kbm90IHN1cHBvcnQgdGhpcyBuZXcgUElNIGhlbGxvIG9wdGlvbj8NCg0KW2hlaWRpXSBG
aXJzdCBvZiBhbGwsIHRoZSBkcmFmdCBzdWdnZXN0IGFuIGFkbWluaXN0cmF0b3IgdG8gY29uZmln
dXJlIERSDQpbaGVpZGldIHByaW9yaXR5IHByb3Blcmx5IHRvIG1ha2Ugc3VyZQ0KW2hlaWRpXSBz
dWNoIGEgdGhpbmcgZG9lc27CuXQgaGFwcGVuIChhbmQgdGhlcmVmb3JlIGZ1bGx5IHRha2UgYWR2
YW50YWdlIG9mDQpbaGVpZGldIHRoZSBpZGVhDQpbaGVpZGldIGRlc2NyaWJlZCBieSB0aGlzIGRy
YWZ0KS4gSWYgdGhlIHVuZm9ydHVuYXRlbHkgaGFwcGVucywgdGhlbiB0aGUNCltoZWlkaV0gbGFu
IGJlaGF2ZXMNCltoZWlkaV0gYWNjb3JkaW5nIHRvIFJGQzQ2MDEuIFRoZXJlIHdpbGwgYmUgbm8g
bG9hZCBiYWxhbmNpbmcuDQoNCuKCrCBXaGF0IGlzIHRoZSBuZWVkIG9mIHNlbmRpbmcgb3V0IHRo
ZSBsaXN0IG9mIEdEUiBieSBQSU0gRFIgdG8gb3RoZXINCnJvdXRlcnM/IE90aGVyIHJvdXRlcnMg
Y2FuIGFueXdheSBmaWd1cmUgdGhpcyBvdXQgYmVjYXVzZSB0aGV5IGFsc28NCnJlY2VpdmUgdGhl
IFBJTSBoZWxsbyBmcm9tIG90aGVyIHJvdXRlcnMuIFJpZ2h0Pw0KDQpbaGVpZGldIFllcywgYnV0
IHRoYXQncyBub3QgYXMgcmVzaWxpZW50Lg0KDQrigqwgSW4gc2VjdGlvbiA4LCAiUElNIERSIExv
YWQgQmFsYW5jaW5nIEhlbGxvIG1lc3NhZ2UiLCBkb2VzIG5vdCBsb29rIHJpZ2h0Lg0KDQpbaGVp
ZGldIGhvdyBhYm91dCAidGhlIG5ldyBEUiBMb2FkIEJhbGFuY2luZyBQSU0gSGVsbG8gT3B0aW9u
cyI/DQoNCg0KdGhhbmtzDQotIEhlaWRpDQoNCg0KDQpPbiA1LzIyLzE0IDEwOjE3IFBNLCAiQmhh
cmF0IEpvc2hpIiA8YmhhcmF0X2pvc2hpQGluZm9zeXMuY29tPiB3cm90ZToNCg0KPk1pa2UsIEF1
dGhvcnMsDQo+DQo+ICAgICAgIEkgaGFkIHNlbnQgc29tZSBxdWVzdGlvbnMvc3VnZ2VzdGlvbnMg
b24gdGhpcyBkcmFmdCBhbG1vc3QgYSB5ZWFyDQo+YmFjay4NCj4NCj4gICAgICAgSGVyZSBpcyB0
aGUgbGluazoNCj5odHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvcGltL2N1cnJl
bnQvbXNnMDI3MjAuaHRtbA0KPg0KPiAgICAgICBJIGFtIG5vdCBzdXJlIGlmIEkgbWlzc2VkIHRo
ZSByZXNwb25zZS4gSSBhbSBhbHNvIG5vdCBzdXJlIGlmDQo+dGhlc2UgaGFzIGJlZW4gYWRkcmVz
c2VzIGluIHRoZSBuZXcgcmV2aXNpb24uDQo+DQo+UmVnYXJkcywNCj5CaGFyYXQgSm9zaGkNCj5o
dHRwOi8vYml0ZS10aGUtYnl0ZXMuYmxvZ3Nwb3QuY29tLw0KPl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj5Gcm9tOiBwaW0gW3BpbS1ib3VuY2VzQGlldGYub3JnXSBv
biBiZWhhbGYgb2YgTWlrZSBNY0JyaWRlDQo+W21pa2UubWNicmlkZUBlcmljc3Nvbi5jb21dDQo+
U2VudDogRnJpZGF5LCBNYXkgMjMsIDIwMTQgMTA6NDAgQU0NCj5UbzogcGltQGlldGYub3JnDQo+
U3ViamVjdDogW3BpbV0gV0dMQzogZHJhZnQtaWV0Zi1waW0tZHJsYi0wMw0KPg0KPlN0aWcgYW5k
IEkgZmVlbCBkcmFmdC1pZXRmLXBpbS1kcmxiLTAzIGlzIHJlYWR5IGZvciBXR0xDLiBUaGUgYXV0
aG9ycw0KPmhhdmUgYWRkcmVzc2VkIGFsbCBjb21tZW50cyB0byBkYXRlLiBUb2RheSBzdGFydHMg
YSB0d28gd2VlayBXR0xDLCBwbGVhc2UNCj5zcGVhayB1cCBlaXRoZXIgd2F5Lg0KPg0KPmh0dHA6
Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtaWV0Zi1waW0tZHJsYi0wMy50eHQNCj4NCj50aGFua3Ms
DQo+bWlrZQ0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+cGltIG1haWxpbmcgbGlzdA0KPnBpbUBpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vcGltDQo+DQo+KioqKioqKioqKioqKioqKiBDQVVUSU9OIC0g
RGlzY2xhaW1lciAqKioqKioqKioqKioqKioqKg0KPlRoaXMgZS1tYWlsIGNvbnRhaW5zIFBSSVZJ
TEVHRUQgQU5EIENPTkZJREVOVElBTCBJTkZPUk1BVElPTiBpbnRlbmRlZA0KPnNvbGVseQ0KPmZv
ciB0aGUgdXNlIG9mIHRoZSBhZGRyZXNzZWUocykuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRl
ZCByZWNpcGllbnQsDQo+cGxlYXNlDQo+bm90aWZ5IHRoZSBzZW5kZXIgYnkgZS1tYWlsIGFuZCBk
ZWxldGUgdGhlIG9yaWdpbmFsIG1lc3NhZ2UuIEZ1cnRoZXIsIHlvdQ0KPmFyZSBub3QNCj50byBj
b3B5LCBkaXNjbG9zZSwgb3IgZGlzdHJpYnV0ZSB0aGlzIGUtbWFpbCBvciBpdHMgY29udGVudHMg
dG8gYW55IG90aGVyDQo+cGVyc29uIGFuZA0KPmFueSBzdWNoIGFjdGlvbnMgYXJlIHVubGF3ZnVs
LiBUaGlzIGUtbWFpbCBtYXkgY29udGFpbiB2aXJ1c2VzLiBJbmZvc3lzDQo+aGFzIHRha2VuDQo+
ZXZlcnkgcmVhc29uYWJsZSBwcmVjYXV0aW9uIHRvIG1pbmltaXplIHRoaXMgcmlzaywgYnV0IGlz
IG5vdCBsaWFibGUgZm9yDQo+YW55IGRhbWFnZQ0KPnlvdSBtYXkgc3VzdGFpbiBhcyBhIHJlc3Vs
dCBvZiBhbnkgdmlydXMgaW4gdGhpcyBlLW1haWwuIFlvdSBzaG91bGQgY2FycnkNCj5vdXQgeW91
cg0KPm93biB2aXJ1cyBjaGVja3MgYmVmb3JlIG9wZW5pbmcgdGhlIGUtbWFpbCBvciBhdHRhY2ht
ZW50LiBJbmZvc3lzDQo+cmVzZXJ2ZXMgdGhlDQo+cmlnaHQgdG8gbW9uaXRvciBhbmQgcmV2aWV3
IHRoZSBjb250ZW50IG9mIGFsbCBtZXNzYWdlcyBzZW50IHRvIG9yIGZyb20NCj50aGlzIGUtbWFp
bA0KPmFkZHJlc3MuIE1lc3NhZ2VzIHNlbnQgdG8gb3IgZnJvbSB0aGlzIGUtbWFpbCBhZGRyZXNz
IG1heSBiZSBzdG9yZWQgb24NCj50aGUNCj5JbmZvc3lzIGUtbWFpbCBzeXN0ZW0uDQo+KioqSU5G
T1NZUyoqKioqKioqIEVuZCBvZiBEaXNjbGFpbWVyICoqKioqKioqSU5GT1NZUyoqKg0KPg0KPl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+cGltIG1haWxp
bmcgbGlzdA0KPnBpbUBpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vcGltDQoNCg0KDQoNCg0KT24gNS8yMi8xNCAxMDoxNyBQTSwgIkJoYXJhdCBKb3NoaSIg
PGJoYXJhdF9qb3NoaUBpbmZvc3lzLmNvbT4gd3JvdGU6DQoNCj5NaWtlLCBBdXRob3JzLA0KPg0K
PiAgICAgICBJIGhhZCBzZW50IHNvbWUgcXVlc3Rpb25zL3N1Z2dlc3Rpb25zIG9uIHRoaXMgZHJh
ZnQgYWxtb3N0IGEgeWVhcg0KPmJhY2suDQo+DQo+ICAgICAgIEhlcmUgaXMgdGhlIGxpbms6DQo+
aHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL3BpbS9jdXJyZW50L21zZzAyNzIw
Lmh0bWwNCj4NCj4gICAgICAgSSBhbSBub3Qgc3VyZSBpZiBJIG1pc3NlZCB0aGUgcmVzcG9uc2Uu
IEkgYW0gYWxzbyBub3Qgc3VyZSBpZg0KPnRoZXNlIGhhcyBiZWVuIGFkZHJlc3NlcyBpbiB0aGUg
bmV3IHJldmlzaW9uLg0KPg0KPlJlZ2FyZHMsDQo+QmhhcmF0IEpvc2hpDQo+aHR0cDovL2JpdGUt
dGhlLWJ5dGVzLmJsb2dzcG90LmNvbS8NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+RnJvbTogcGltIFtwaW0tYm91bmNlc0BpZXRmLm9yZ10gb24gYmVoYWxmIG9m
IE1pa2UgTWNCcmlkZQ0KPlttaWtlLm1jYnJpZGVAZXJpY3Nzb24uY29tXQ0KPlNlbnQ6IEZyaWRh
eSwgTWF5IDIzLCAyMDE0IDEwOjQwIEFNDQo+VG86IHBpbUBpZXRmLm9yZw0KPlN1YmplY3Q6IFtw
aW1dIFdHTEM6IGRyYWZ0LWlldGYtcGltLWRybGItMDMNCj4NCj5TdGlnIGFuZCBJIGZlZWwgZHJh
ZnQtaWV0Zi1waW0tZHJsYi0wMyBpcyByZWFkeSBmb3IgV0dMQy4gVGhlIGF1dGhvcnMNCj5oYXZl
IGFkZHJlc3NlZCBhbGwgY29tbWVudHMgdG8gZGF0ZS4gVG9kYXkgc3RhcnRzIGEgdHdvIHdlZWsg
V0dMQywgcGxlYXNlDQo+c3BlYWsgdXAgZWl0aGVyIHdheS4NCj4NCj5odHRwOi8vd3d3LmlldGYu
b3JnL2lkL2RyYWZ0LWlldGYtcGltLWRybGItMDMudHh0DQo+DQo+dGhhbmtzLA0KPm1pa2UNCj4N
Cj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPnBpbSBt
YWlsaW5nIGxpc3QNCj5waW1AaWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3BpbQ0KPg0KPioqKioqKioqKioqKioqKiogQ0FVVElPTiAtIERpc2NsYWltZXIg
KioqKioqKioqKioqKioqKioNCj5UaGlzIGUtbWFpbCBjb250YWlucyBQUklWSUxFR0VEIEFORCBD
T05GSURFTlRJQUwgSU5GT1JNQVRJT04gaW50ZW5kZWQNCj5zb2xlbHkgDQo+Zm9yIHRoZSB1c2Ug
b2YgdGhlIGFkZHJlc3NlZShzKS4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVu
dCwNCj5wbGVhc2UgDQo+bm90aWZ5IHRoZSBzZW5kZXIgYnkgZS1tYWlsIGFuZCBkZWxldGUgdGhl
IG9yaWdpbmFsIG1lc3NhZ2UuIEZ1cnRoZXIsIHlvdQ0KPmFyZSBub3QgDQo+dG8gY29weSwgZGlz
Y2xvc2UsIG9yIGRpc3RyaWJ1dGUgdGhpcyBlLW1haWwgb3IgaXRzIGNvbnRlbnRzIHRvIGFueSBv
dGhlcg0KPnBlcnNvbiBhbmQgDQo+YW55IHN1Y2ggYWN0aW9ucyBhcmUgdW5sYXdmdWwuIFRoaXMg
ZS1tYWlsIG1heSBjb250YWluIHZpcnVzZXMuIEluZm9zeXMNCj5oYXMgdGFrZW4gDQo+ZXZlcnkg
cmVhc29uYWJsZSBwcmVjYXV0aW9uIHRvIG1pbmltaXplIHRoaXMgcmlzaywgYnV0IGlzIG5vdCBs
aWFibGUgZm9yDQo+YW55IGRhbWFnZSANCj55b3UgbWF5IHN1c3RhaW4gYXMgYSByZXN1bHQgb2Yg
YW55IHZpcnVzIGluIHRoaXMgZS1tYWlsLiBZb3Ugc2hvdWxkIGNhcnJ5DQo+b3V0IHlvdXIgDQo+
b3duIHZpcnVzIGNoZWNrcyBiZWZvcmUgb3BlbmluZyB0aGUgZS1tYWlsIG9yIGF0dGFjaG1lbnQu
IEluZm9zeXMNCj5yZXNlcnZlcyB0aGUgDQo+cmlnaHQgdG8gbW9uaXRvciBhbmQgcmV2aWV3IHRo
ZSBjb250ZW50IG9mIGFsbCBtZXNzYWdlcyBzZW50IHRvIG9yIGZyb20NCj50aGlzIGUtbWFpbCAN
Cj5hZGRyZXNzLiBNZXNzYWdlcyBzZW50IHRvIG9yIGZyb20gdGhpcyBlLW1haWwgYWRkcmVzcyBt
YXkgYmUgc3RvcmVkIG9uDQo+dGhlIA0KPkluZm9zeXMgZS1tYWlsIHN5c3RlbS4NCj4qKipJTkZP
U1lTKioqKioqKiogRW5kIG9mIERpc2NsYWltZXIgKioqKioqKipJTkZPU1lTKioqDQo+DQo+X19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5waW0gbWFpbGlu
ZyBsaXN0DQo+cGltQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9waW0NCg0K


From nobody Wed May 28 12:50:27 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 160931A0674 for <pim@ietfa.amsl.com>; Wed, 28 May 2014 12:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 0QjIpQ6UYq8E for <pim@ietfa.amsl.com>; Wed, 28 May 2014 12:50:23 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 5EFAB1A0665 for <pim@ietf.org>; Wed, 28 May 2014 12:50:23 -0700 (PDT)
Received: from [10.154.208.178] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 7261B8034 for <pim@ietf.org>; Wed, 28 May 2014 21:50:18 +0200 (CEST)
Message-ID: <53863DF4.9070405@venaas.com>
Date: Wed, 28 May 2014 12:50:12 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "pim@ietf.org" <pim@ietf.org>
References: <6F5149063CE40341BE7953160A93C5A0EE8211@eusaamb109.ericsson.se>
In-Reply-To: <6F5149063CE40341BE7953160A93C5A0EE8211@eusaamb109.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/2XDHqdn2RiHI7R_QcAOS1d23H2Q
Subject: Re: [pim] WGLC: draft-ietf-pim-drlb-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 May 2014 19:50:27 -0000

Hi

I think the draft is in a good shape, but here are some comments.

Please check the nits at
http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-pim-drlb-03.txt

As it says, you should use the official IPv4 example addresses in
RFC 5737, not private addresses. Note that for multicast we also
have RFC 6676.

There are also issues with references.


You should write "PIM-SM" rather than "PIM SM" throughout. "PIM-SM"
is what is used in 4601 and also defined at
https://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

Use Mbps and Gbps rather than mbps and gpbs?

In 2 you say it is a modification to the PIM protocol. I think it
is more correct to say that it is to PIM-SM.

In 4 it says

    Hello Option.  Besides that, a DR Load Balancing Capability (DRLBC)
    Hello Option, which contains hash algorithm type, is also announced
    by router interfaces which have this specification supported.  Last

I think it should say "enabled" rather than "supported". Perhaps say
"is also announced by the router on interfaces where this specification
is enabled". I think it is important to make this distinction since many
routers might support it, but you may only want to use this mechanism on
certain interfaces on certain routers.

It also says "hop routers who are with the new DRLBC Option". Maybe
phrase this more clearly. "who are with" seems a bit unclear to me.

At end of 4 it says

    A hash algorithm based on the announced Source, Group or RP masks
    allows one GDR to be assigned to a corresponding multicast group, and
    that GDR is responsible for initiating the creation of the multicast
    forwarding tree for the group.

When you hash on source address it would be a GDR for the (S,G), right?
You cold have different GDRs for (S1,G) and (S2,G).

In 4.2 you first describe the hash masks which I think are fairly
independent of the algorithm. But then you describe the use of modulo.
It would be good to make it even clearer what is independent and what
is algorithm specific. Maybe a separate subsection, or a sentence saying
that the rest of this sub section is algorithm specific?

Beginning of 4.3 it says:

    When a last hop PIM router sends a PIM Hello from an interface with
    this specificiation support, it includes a new option, called "Load
    Balancing Capability (DRLBC)".

Typo of "specification". Maybe say with this specification enabled.

5.1 also "enabled" rather than "supports".
State that it only applies to the address family of the source address
of the Hellop IP header.

5.2 State what the length would be for IPv4 and IPv6?
State that all addresses should be of the same family as the Hello IP
header?

End of 6.1:
    Candidate and insert the neighbor's address into the sorted list of
    DRLBGRD Option.

Maybe mention briefly the Router-ID here since not always the neighbor's
address.

6.2
Most of this section is algorithm specific. As I noted in 4.2 it would
be good to make it very clear which parts are algorithm specific. So
good to point that out. Would it make sense to put the algorithm
specific parts in one common section? The last part of 6.2 looks
independent of the algorithm.

    Candidates.  The hasvalue_RP for RP1 172.3.10.10 is 0, matches the
typo                ^^^^^^^^^^^

Use documentation addresses in this section.

7.
Might be good to point out that the values have already been preassigned.

Stig



From nobody Wed May 28 13:20:58 2014
Return-Path: <sami.biz.email@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 248B31A068F for <pim@ietfa.amsl.com>; Wed, 28 May 2014 13:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.155
X-Spam-Level: 
X-Spam-Status: No, score=0.155 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, FRT_BELOW2=2.154, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 re6nRPMCJMZ3 for <pim@ietfa.amsl.com>; Wed, 28 May 2014 13:20:53 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5DAE1A0680 for <pim@ietf.org>; Wed, 28 May 2014 13:20:52 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id x12so11646079wgg.33 for <pim@ietf.org>; Wed, 28 May 2014 13:20:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=kI6MYL48xR6qAoDXDIq51Ro81APLZZXI2gajd0czDks=; b=zfI1ORZARwRavF0E0fghOhEcnmLkJXWxGi6xRVwhaA8ZZuyFvZvQSJex/G5UYRd1Wm LmVF6ucYSRV6LxICO1ZfbQFhffE2D+U0byQi9DYMvgAuqAkNtzMsY3gMdLj3bnj8tEZ6 w+b7vXjexs36IncrUUONpVvRdI4YyOn08kq/djHfv6ERTuy8kilLBkaOQsUEt6Kx2mni WbvHCB6+rsRA6JbPBV2yz6VbpOlLofKdJy2FsyC6+HvWp/ZpNXzN7lX3g4nUC/dH6ViS 35LIWabHm/HGx5sMQKLzkF3r5jyoh5ZpZFDS/rQymugiS71jJpjQKdWwEde4fiaLaMX1 uXtw==
X-Received: by 10.180.72.243 with SMTP id g19mr52680358wiv.44.1401308447949; Wed, 28 May 2014 13:20:47 -0700 (PDT)
Received: from [192.168.1.3] ([178.253.63.64]) by mx.google.com with ESMTPSA id k2sm45818910wjq.20.2014.05.28.13.20.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 28 May 2014 13:20:47 -0700 (PDT)
Message-ID: <53865240.3050409@gmail.com>
Date: Thu, 29 May 2014 00:46:48 +0330
From: saeed sami <sami.biz.email@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: pim@ietf.org, pim-chairs@tools.ietf.org
Content-Type: multipart/alternative; boundary="------------040504070601070302070704"
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/ymKo5dOaUEdepzzExlEWfQ3ffLg
Subject: [pim] draft-sami-pim-ng-02 PIM-NG advantages (part 2)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 May 2014 20:20:55 -0000

This is a multi-part message in MIME format.
--------------040504070601070302070704
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello.

This email might be a little too long but it is worth reading and I hope 
that it will be read by WG experts.  It is related to some of the 
advantages of PIM-NG the new proposed PIM protocol. The draft can be 
find at:

http://tools.ietf.org/html/draft-sami-pim-ng-02

since It was not possible to send the email at once I will have to send 
it to the mailing list  in separate parts , and this is part2 of the series.

Some of the key advantages of PIM-NG that can make it a potential 
candidate for adoption by the WG are explained bellow:


6-Since the role of an RP is similar to an information station which 
only helps last hop routers (clients) find the source of a multicast 
traffic (G), large number of last hops won't cause any problem in a 
PIM-NG domain. This is achieved due to the fact that the RP doesn't need 
to save the state of every (*, G) join it receives before a last hop 
switches to SPT and actually there is no RPT tree formations.

7-Since as soon as a source is registered with the RP, clients (last hop 
router) will only need to send a unicast-encapsulated request for source 
message to the RP and as soon as the unicast address of the source is 
received back from the RP they will join the SPT tree there will be no 
delay at all in communicating with a source and receiving the multicast 
traffic it represents.

8-PIM-NG uses a new ANYCAST RP and Mesh-Group concept, which if 
implemented correctly, allows for the existence of many RPs in a single 
multicast domain while reducing the network resource consumption by the 
multicast introduction messages sent by RPs and also reduces the amount 
of Active source advertisements within a domain. In a single multicast 
domain the number of existing RPs can be up to 255 RPs which if the 
PIM-NG Sub-Domain concept is implemented correctly , the number of 
existing RPs in a multicast domain can be increased to up to 254*255 
conceptually , which will provide high availability in its maximum level.

9-Since the current multicast domain definition and RPF check method in 
use by PIM-SM and MSDP doesn't allow the existence of transitory 
Autonomous System'(s) or multicast domains, PIM-NG introduces its unique 
multicast domain concept alongside a new RPF check method unique to 
PIM-NG specifications which allows the existence of transitory multicast 
domains.

10-The new RPF check method introduced in PIM-NG gives a higher level of 
control and security with regards to propagation and advertisement of 
the information regarding the active sources. Dou to its nature which 
allows the existence of transitory multicast domains and because the RPF 
check method and how different multicast domains are connected in 
PIM-NG, administrators will have a flexible and easy control over the 
Active sources advertisements.

11-Because of the new and unique multicast domain concept introduced, 
PIM-NG provides a higher level of control over multicast networks 
through the concept of Sub-Domain alongside a higher level of security 
which is indeed a positive factor for any protocol through the 
implementation of Stub-Domains. Both of the concepts are unique to PIM-NG.

End of part 2.
-- 
sincerely yours
MR.SAEED SAMI

--------------040504070601070302070704
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p class="MsoNormal" style="direction:ltr">Hello.</p>
    <p class="MsoNormal" style="direction:ltr">This
      email might be a little too long but it is worth reading and I
      hope that it
      will be read by WG experts.&nbsp; It is
      related to some of the advantages of PIM-NG the new proposed PIM
      protocol. The draft
      can be find at: </p>
    <p class="MsoNormal" style="direction:ltr">&nbsp;<a
        href="http://tools.ietf.org/html/draft-sami-pim-ng-02">http://tools.ietf.org/html/draft-sami-pim-ng-02</a>
      &nbsp;</p>
    <p class="MsoNormal" style="direction:ltr">since
      It was not possible to send the email at once I will have to send
      it to the
      mailing list &nbsp;in separate parts , and
      this is part2 of the series.</p>
    <p class="MsoNormal" style="direction:ltr">Some
      of the key advantages of PIM-NG that can make it a potential
      candidate for
      adoption by the WG are explained bellow:</p>
    <p class="MsoNormal" style="direction:ltr"><br>
    </p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">6-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>Since the role of an RP is
      similar to an information station which only helps last hop
      routers (clients)
      find the source of a multicast traffic (G), large number of last
      hops won't cause
      any problem in a PIM-NG domain. This is achieved due to the fact
      that the RP
      doesn&#8217;t need to save the state of every (*, G) join it receives
      before a last
      hop switches to SPT and actually there is no RPT tree formations.</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">7-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>Since as soon as a source
      is registered with the RP, clients (last hop router) will only
      need to send a
      unicast-encapsulated request for source message to the RP and as
      soon as the
      unicast address of the source is received back from the RP they
      will join the
      SPT tree there will be no delay at all in communicating with a
      source and
      receiving the multicast traffic it represents.</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">8-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>PIM-NG uses a new ANYCAST
      RP and Mesh-Group concept, which if implemented correctly, allows
      for the existence
      of many RPs in a single multicast domain while reducing the
      network resource
      consumption by the multicast introduction messages sent by RPs and
      also reduces
      the amount of Active source advertisements within a domain. In a
      single
      multicast domain the number of existing RPs can be up to 255 RPs
      which if the
      PIM-NG Sub-Domain concept is implemented correctly , the number of
      existing RPs
      in a multicast domain can be increased to up to 254*255
      conceptually , which
      will provide high availability in its maximum level.</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">9-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>Since the current multicast
      domain definition and RPF check method in use by PIM-SM and MSDP
      doesn&#8217;t allow
      the existence of transitory Autonomous System'(s) or multicast
      domains, PIM-NG
      introduces its unique multicast domain concept alongside a new RPF
      check method
      unique to PIM-NG specifications which allows the existence of
      transitory
      multicast domains.</p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">10-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>The new RPF check method
      introduced in PIM-NG gives a higher level of control and security
      with regards
      to propagation and advertisement of the information regarding the
      active
      sources. Dou to its nature which allows the existence of
      transitory multicast
      domains and because the RPF check method and how different
      multicast domains
      are connected in PIM-NG, administrators will have a flexible and
      easy control
      over the Active sources advertisements. </p>
    <p class="MsoNormal" style="direction:ltr">
    </p>
    <p class="" style="margin:0cm 0cm 10pt 36pt;direction:ltr">11-<span
        style="font-size:7pt;font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span><span dir="LTR"></span>Because of the new and
      unique multicast domain concept introduced, PIM-NG provides a
      higher level of
      control over multicast networks through the concept of Sub-Domain
      alongside a
      higher level of security which is indeed a positive factor for any
      protocol
      through the implementation of Stub-Domains. Both of the concepts
      are unique to
      PIM-NG.</p>
    <div>End of part 2.</div>
    -- <br>
    sincerely yours<br>
    MR.SAEED SAMI
  </body>
</html>

--------------040504070601070302070704--


From nobody Wed May 28 15:44:45 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 806D51A0715 for <pim@ietfa.amsl.com>; Wed, 28 May 2014 15:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.254
X-Spam-Level: 
X-Spam-Status: No, score=0.254 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_BELOW2=2.154] autolearn=no
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 aKG3KVzaY2ea for <pim@ietfa.amsl.com>; Wed, 28 May 2014 15:44:42 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB031A0272 for <pim@ietf.org>; Wed, 28 May 2014 15:44:42 -0700 (PDT)
Received: from [10.154.208.178] (128-107-239-235.cisco.com [128.107.239.235]) by ufisa.uninett.no (Postfix) with ESMTPSA id 9C78C8025; Thu, 29 May 2014 00:44:37 +0200 (CEST)
Message-ID: <538666D3.4070008@venaas.com>
Date: Wed, 28 May 2014 15:44:35 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: saeed sami <sami.biz.email@gmail.com>, pim@ietf.org,  pim-chairs@tools.ietf.org
References: <53852E73.9000507@gmail.com>
In-Reply-To: <53852E73.9000507@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/8LfT1vcQO-h4_Bv7paoLulzbHoE
Subject: Re: [pim] draft-sami-pim-ng-02 PIM-NG advantages (part 1)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 May 2014 22:44:43 -0000

It would be nice if others could also take a look at these advantages,
and ideally also the proposal, and provide some comments.

Stig

On 5/27/2014 5:31 PM, saeed sami wrote:
> Hello.
>
> This email might be a little too long but it is worth reading since it
> is about some of the key advantages of the new proposed protocol, and I
> hope that it will be read by WG experts.  It is related to some of the
> advantages of PIM-NG the new proposed PIM protocol. The draft can be
> find at:
>
> http://tools.ietf.org/html/draft-sami-pim-ng-02
>
> since It was not possible to send the email at once I will have to send
> it to the mailing list  in separate parts , and this is part 1 of the
> series.
>
> Some of the key advantages of PIM-NG that can make it a potential
> candidate for adoption by the WG are explained bellow:
>
> 1-Different concepts of PIM-NG with regards to RP discovery and other
> processes are designed in a way to provide an easy to implement (to some
> extents), automatic or intelligent routing protocol to some extents.
> This is achieved by introducing new processes and packet types which
> allow PIM-NG components such as C-RP's, C-MAPPER's and … to converge and
> fin each other automatically and in the lowest time interval.
>
> 2-the definition and role of existing RP'(S) and BSR'(s) weren't clear
> at least to my eyes which guided me towards a little bit different
> definition with regards to how the exiting components of a PIM-NG
> multicast network are introduced to the PIM-NG population.
>
> 3-A PIM-NG MAPPER which can be considered as a BSR too, has a more vital
> role in PIM-NG which makes it possible to follow a hierarchical design
> pattern.
>
> 4-PIM-NG uses a new source register process which makes the size of
> register packets smaller due to the fact that there will be no need for
> data packet to be sent alongside the register message.  This will reduce
> the bandwidth and resource consumption since no data packet is sent in a
> register message.
>
> 5-The source discovery method used by PIM-SM seemed a little
> un-optimized in parts mainly related to a last hop router joining the
> RPT rooted at the RP first and then switch to SPT. This process is not
> necessary and is network resource consuming. So a new process is defined
> in PIM-NG which eliminates the need for the (*, G) RPT tree to form
> first. The new source discovery method puts PIM-NG one cycle a head of
> PIM-SM in finding and communicating with a source.
>
> End of part 1.
> --
> sincerely yours
> MR.SAEED SAMI


From nobody Thu May 29 21:37:13 2014
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E1B31A076F for <pim@ietfa.amsl.com>; Thu, 29 May 2014 21:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 naI7E837HRwT for <pim@ietfa.amsl.com>; Thu, 29 May 2014 21:37:07 -0700 (PDT)
Received: from KECGATE03.infosys.com (kecgate03.infosysconsulting.com [122.98.10.31]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 674A31A06E2 for <pim@ietf.org>; Thu, 29 May 2014 21:37:06 -0700 (PDT)
X-TM-IMSS-Message-ID: <9df2739a0005bd55@infosys.com>
Received: from BLRKECHUB11.ad.infosys.com ([10.66.236.43]) by infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service 7.1) id 9df2739a0005bd55 ; Fri, 30 May 2014 10:01:43 +0530
Received: from BLRKECHUB06.ad.infosys.com (10.66.236.116) by BLRKECHUB11.ad.infosys.com (10.66.236.43) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 30 May 2014 10:02:26 +0530
Received: from BLRKECMBX12.ad.infosys.com ([fe80::a0dd:c35f:79ad:4993]) by BLRKECHUB06.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Fri, 30 May 2014 10:02:25 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "Heidi Ou (hou)" <hou@cisco.com>, Mike McBride <mike.mcbride@ericsson.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] WGLC: draft-ietf-pim-drlb-03
Thread-Index: Ac92RKTTcHNidFXpQ2G8zQt0EgQ/KQAAWIYyARL1d4AASm8sEA==
Date: Fri, 30 May 2014 04:32:24 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED4858BD44@BLRKECMBX12.ad.infosys.com>
References: <35347FBF2796F94E936EE76C0E6047ED4858ACDB@BLRKECMBX12.ad.infosys.com>,  <CFAB6B69.9D39A%hou@cisco.com>
In-Reply-To: <CFAB6B69.9D39A%hou@cisco.com>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.200.132]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/MVzHavsncaOitObuDBALIty4wMU
Subject: Re: [pim] WGLC: draft-ietf-pim-drlb-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 30 May 2014 04:37:11 -0000

Hi Heidi,

      Thanks for your response. Please see my response in line with '<Bhara=
t>:'

Regards,
Bharat Joshi
http://bite-the-bytes.blogspot.com/
________________________________________
From: Heidi Ou (hou) [hou@cisco.com]
Sent: Wednesday, May 28, 2014 11:58 PM
To: Bharat Joshi; Mike McBride; pim@ietf.org
Subject: Re: [pim] WGLC: draft-ietf-pim-drlb-03

Hi Bharat,

Thanks for your comments, sorry to reply this late, but
we have made quite a few changes since -02- (latest is -03-),
especially in section 6.2 and 6.3.

Please find reply inline, search for [heidi]



From: Bharat Joshi
Sent: Friday, June 28, 2013 4:09 PM
To: pim at ietf.org
Subject: Few questions/suggestion on DR Load Balancing draft

Hi,

       I just read through the DR Load Balancing draft. I have few
questions/suggestion below.

Regards,
Bharat

=80 In Abstract, s/as an Ethernet/as Ethernet/g. This seems to be at couple
of places.


[heidi] Ok

[heidi] I will try to fix some of the obvious errors and follow up with
[heidi] chairs to see how we can get such a review done.
[heidi] I remember we have a review specifically for the proper and
[heidi] accurate use of the English language in an I-D.

<Bharat>: Ok.

=80 Are 'first hop network' or 'last hop LAN' a well known term? Will it be
easy for people to understand that this is being talked from multicast
source perspective? Can we call them directly connected LAN in both the
cases?

[heidi] They are well-known.  Googling =B3pim first hop=B2 will generate
reference from several different sources.



=80 In Abstract, s/is operated in PIM SM/is operating in PIM SM/g. This is
at least at two places.

[heidi] done


=80 In Abstract, in following sentence:

On the last hop network, the PIM DR is responsible for tracking local
multicast listeners and forwarding traffic to these listeners if the group
is operated in PIM SM/SSM/DM.

Should we mentioning BIDIR-PIM as well in this list? Or such a group is
treated differently?


[heidi] The concept of PIM-DR is not relevant for Bidir-PIM.  In
[heidi] Bidir-PIM, it is the DF that handles forwarding.

<Bharat>: Ok.

=80 In Abstract, s/can be distributed to and handled among these/can be
distributed among these/

[heidi] done


=80 In GDR definition, it talks about that GDR is responsible for a group.
Does this mean that a single GDR will be responsible for all channels
(S,G) for a given group but different sources?

[heidi] Which flow, i.e., (S,G), a GDR is responsible for depends on the
[heidi] hash function.

<Bharat>: I looked at the text in current draft. It looked ok to me.

=80 s/process received new PIM Hello/process new PIM Hello/

=80 In Introduction, in following sentence:

According to [RFC4601], R1 will be responsible for forwarding to the last
hop LAN.

       Can we replace this sentence by something similar to a sentence
from RFC 4601, section 6.1.1 point 2. The sentence is as follows:

The designated router on a LAN is (in the absence of asserts) responsible
for forwarding traffic to that LAN on behalf of any local members.


[heidi] sure.


=80 There may be a mix of local hosts as well as downstream routers in a
network scenario. Do we still call this the last hop LAN? I guess yes and
I think there can still be GDR candidate and this draft can apply. Right?
I think this is not coming out well in the draft. So please add/update
some text to reflect this.

[heidi] The draft should still apply in the scenario described.

=80 In section 3, I did not get what 'load balancing' are we talking about
in case of 'first hop routers'?

[heidi] It is referring to the common implementation that when a downstream
[heidi] router has multiple upstream neighbors that are equal cost as
[heidi] determined by IGP,
[heidi] it will =B3load balance=B2 the joins when choosing an upstream
[heidi] neighbor.

<Bharat>: I still did not fully get this. Is this for source or a RP? Won't=
 there be multiple multicast stream get forwarded to the LAN and then asser=
t will choose one forwarder. Why would we want to do this?

=80 In section 3, I also did not understand how ECMP helps in this load
balancing. If there are multiple routers on a LAN in which the source also
sits, as per PIM, its the DR who is to send the register messages to the
RP. So I am not sure how ECMP helps here in making other router on this
LAN to do this instead of the DR?

[heidi] Yes it is the DR that sends the registers.  But the packets are
[heidi] mostly forwarded natively
[heidi] down the source trees established by (S,G) joins from downstream
[heidi] routers.

<Bharat>: As mentioned above, I am still not clear about this.

=80 As per RFC 4601, PIM DR is elected for any type of networks so there is
no need to mention that PIM DR election is done in a multi-access network.

[heidi] I am missing the your point here.

<Bharat>: What I was trying to suggest is that this draft does not need to =
mention that a DR election is done in multi-access network. It can just ref=
er to RFC 4601.

=80 In section 4, in sentence "The PIM DR is responsible for sending
Join/Prune messages to the RP or source.", I think we should mention that
this is done for the local host's join/leave.

[heidi] That would be redundant. If it is not for local hosts, then it
[heidi] doesn=B9t matter whether the router is a DR or not on the interface
[heidi] from which a PIM Join/Prune is received.

<Bharat>: Exactly, a DR router may or may not send PIM join/prune to RP bec=
ause that will depend upon whether DR is the upstream router or not. But in=
 case of local joins, DR has the responsibility to do it and hence to make =
the above statement complete, it will be better to add that this is for loc=
al joins.

=80 In section 4, para 1, I think it should be enough if the text suggest
that PIM DR election is done as per RFC 4601 instead of describing the
algorithm here.

[heidi] We will keep the text. Another reviewer might wish to have the
[heidi] additional description.

<Bharat>: Ok.


=80 s/routers support this specification/routers which support this
Specification/

[heidi] ok.

=80 In section 4, can we reword the following sentence:

Last hop routers who are with the new LBC TLV and with the same DR
priority as the PIM DR are GDR Candidates.

to

Last hop routers which supports the 'Load Balancing Capability' PIM hello
option and uses the same DR priority as the PIM DR, are considered to be
GDR Candidates.

[heidi] ok

=80 In section 4, last para, can we clearly mention that we are referring t=
o
groups joined by local members only.

[heidi] As mentioned early, The context of this draft is for directly
[heidi] attached host. We are not modifying any behavior of a PIM router
[heidi] when it receives a PIM Join/Prune.

<Bharat>: Ok.

=80 I think section 4.2 should be divided into two, one that defined hash
mask and another that defines the hash function.

[heidi] it is not a large paragraph, we will keep it as is.

<Bharat>:Ok.

=80 Apart from the hash value/function, cannot an administrator configure
the mapping statically? This way, an administrator will have more control
on which channel is registered by which DR and also, he won't need these
new hello options. I agree that such a thing will work only if all vendors
provide such a mean to the administrators.

[heidi] Correct. We are trying to reduce unnecessary configuration, and
[heidi] reduce the possibility of inconsistency.



=80 In section 4.3, its not clear what will be the contents of first PIM
hello message of a router coming up? Will it contain LB GDR option or not?
At that time, it may not know whether its a DR or not. Actually, it will
assume that its the DR until it receives a hello message from a higher DR
priority router.


[heidi] It depends on the implementation=B9s choice whether it considers
[heidi] itself as a DR when the interface comes up.
[heidi] The draft doesn=B9t intend to dictate that choice. IT just specifie=
s
[heidi] what to send.

<Bharat>: But would it create any interoperability issue? If one router ass=
umes that it must come in the first PIM message and another does not send i=
t in first PIM message.

=80 In section 5.2, should we be using encoded format defined in RFC 4601
for GDR addresses or using it in native format is fine?

[heidi] The encoded format doesn=B9t handle non-contiguous mask.

<Bharat>: Ok.

=80 What is the idea of sending the masks from PIM DR to other routers? Why
cannot they be configured in all the routers?
[heidi] yes, but we want to use the protocol to handle this automatically,
and consistently.

<Bharat>:Ok.

=80 s/When an IGMP join is received/When an IGMP/MLD join is received/
=80 s/a neighbor Hello with/a PIM Hello with/

[heidi] ok


=80 What happens when a PIM router supporting this new options times out in
PIM DR router?

[heidi] Then another router will become the DR and take over the
[heidi] responsibility.




=80 Does PIM DR insert its own address as well in the neighbor's address
into the LBGRD TLV list?

[heidi] yes.

=80 In section 6.2, first para talks about router R1. Is it referring to
figure 1?

[heidi] It's actually just referring to PIM DR. I will remove it,
[heidi] just saying "PIM DR".

<Bharat>: Ok.

=80 In section 6.2, should not we mention what a GDR candidate does when a
PIM hello from PIM DR is received? I think few last paras at the end of
this section should be in the front. Please check.

[heidi] Could you please be more specific about what is missing and
[heidi] suggest text?

<Bharat>: I am sorry but I am not able to recall this.

=80 s/from a non-DR PIM router/from a PIM router which is not DR/

[heidi] ok

=80 In section 6.2, its not clear if the hash is calculated only for 'X' or
for all the GDR available in the list. I think it needs to be calculated
for all of them and then if hash is highest for 'X', its selected,
otherwise not.

[heidi] In the latest version, -03-, the hash value is computed for X
[heidi] only. If the hash value matches the ordinal number assigned to X, X
[heidi] will be the GDR.

<Bharat>:Ok.

=80 In section 6.3, in case of PIM assert, should not we override the
existing Assert algorithm completely and suggest that the winner should be
selected based on the currently selected GDR?

[heidi] Could you please elaborate the reasons why 6.3 is insufficient in
[heidi] this case?

<Bharat>: What I was trying to ask is that is there really a need to sugges=
t modifications in assert mechanism. Instead, let the assert mechanism use =
the existing algorithm as it is. The only thing we need is that we would wa=
nt to reduce the traffic loss which can be avoided by making R1 and R2 not =
stopping the forwarding.

<Bharat>: Also, I was just reading the text in this section in version 03. =
I think there is a small typo in
<Bharat>: "When R3 comes up online, it is possible that R3 becomes GDR for =
both G1 and G2, hence
<Bharat>: R2 starts to build the forwarding tree for G1 and G2"
<Bharat>: I think it should say "R3 starts to build".

=80 What happens when a new router comes up which becomes the DR but does
not support this new PIM hello option?

[heidi] First of all, the draft suggest an administrator to configure DR
[heidi] priority properly to make sure
[heidi] such a thing doesn=B9t happen (and therefore fully take advantage o=
f
[heidi] the idea
[heidi] described by this draft). If the unfortunately happens, then the
[heidi] lan behaves
[heidi] according to RFC4601. There will be no load balancing.

<Bharat>: OK.

=80 What is the need of sending out the list of GDR by PIM DR to other
routers? Other routers can anyway figure this out because they also
receive the PIM hello from other routers. Right?

[heidi] Yes, but that's not as resilient.

<Bharat>: Ok.

=80 In section 8, "PIM DR Load Balancing Hello message", does not look righ=
t.

[heidi] how about "the new DR Load Balancing PIM Hello Options"?

<Bharat>: Yeah, Ok.


thanks
- Heidi



On 5/22/14 10:17 PM, "Bharat Joshi" <bharat_joshi@infosys.com> wrote:

>Mike, Authors,
>
>       I had sent some questions/suggestions on this draft almost a year
>back.
>
>       Here is the link:
>http://www.ietf.org/mail-archive/web/pim/current/msg02720.html
>
>       I am not sure if I missed the response. I am also not sure if
>these has been addresses in the new revision.
>
>Regards,
>Bharat Joshi
>http://bite-the-bytes.blogspot.com/
>________________________________________
>From: pim [pim-bounces@ietf.org] on behalf of Mike McBride
>[mike.mcbride@ericsson.com]
>Sent: Friday, May 23, 2014 10:40 AM
>To: pim@ietf.org
>Subject: [pim] WGLC: draft-ietf-pim-drlb-03
>
>Stig and I feel draft-ietf-pim-drlb-03 is ready for WGLC. The authors
>have addressed all comments to date. Today starts a two week WGLC, please
>speak up either way.
>
>http://www.ietf.org/id/draft-ietf-pim-drlb-03.txt
>
>thanks,
>mike
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www.ietf.org/mailman/listinfo/pim
>
>**************** CAUTION - Disclaimer *****************
>This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
>solely
>for the use of the addressee(s). If you are not the intended recipient,
>please
>notify the sender by e-mail and delete the original message. Further, you
>are not
>to copy, disclose, or distribute this e-mail or its contents to any other
>person and
>any such actions are unlawful. This e-mail may contain viruses. Infosys
>has taken
>every reasonable precaution to minimize this risk, but is not liable for
>any damage
>you may sustain as a result of any virus in this e-mail. You should carry
>out your
>own virus checks before opening the e-mail or attachment. Infosys
>reserves the
>right to monitor and review the content of all messages sent to or from
>this e-mail
>address. Messages sent to or from this e-mail address may be stored on
>the
>Infosys e-mail system.
>***INFOSYS******** End of Disclaimer ********INFOSYS***
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www.ietf.org/mailman/listinfo/pim





On 5/22/14 10:17 PM, "Bharat Joshi" <bharat_joshi@infosys.com> wrote:

>Mike, Authors,
>
>       I had sent some questions/suggestions on this draft almost a year
>back.
>
>       Here is the link:
>http://www.ietf.org/mail-archive/web/pim/current/msg02720.html
>
>       I am not sure if I missed the response. I am also not sure if
>these has been addresses in the new revision.
>
>Regards,
>Bharat Joshi
>http://bite-the-bytes.blogspot.com/
>________________________________________
>From: pim [pim-bounces@ietf.org] on behalf of Mike McBride
>[mike.mcbride@ericsson.com]
>Sent: Friday, May 23, 2014 10:40 AM
>To: pim@ietf.org
>Subject: [pim] WGLC: draft-ietf-pim-drlb-03
>
>Stig and I feel draft-ietf-pim-drlb-03 is ready for WGLC. The authors
>have addressed all comments to date. Today starts a two week WGLC, please
>speak up either way.
>
>http://www.ietf.org/id/draft-ietf-pim-drlb-03.txt
>
>thanks,
>mike
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www.ietf.org/mailman/listinfo/pim
>
>**************** CAUTION - Disclaimer *****************
>This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
>solely
>for the use of the addressee(s). If you are not the intended recipient,
>please
>notify the sender by e-mail and delete the original message. Further, you
>are not
>to copy, disclose, or distribute this e-mail or its contents to any other
>person and
>any such actions are unlawful. This e-mail may contain viruses. Infosys
>has taken
>every reasonable precaution to minimize this risk, but is not liable for
>any damage
>you may sustain as a result of any virus in this e-mail. You should carry
>out your
>own virus checks before opening the e-mail or attachment. Infosys
>reserves the
>right to monitor and review the content of all messages sent to or from
>this e-mail
>address. Messages sent to or from this e-mail address may be stored on
>the
>Infosys e-mail system.
>***INFOSYS******** End of Disclaimer ********INFOSYS***
>
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www.ietf.org/mailman/listinfo/pim


From nobody Fri May 30 12:09:27 2014
Return-Path: <hou@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E73E51A7029 for <pim@ietfa.amsl.com>; Fri, 30 May 2014 12:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 R38-GUxQHlrk for <pim@ietfa.amsl.com>; Fri, 30 May 2014 12:09:22 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF6EE1A7026 for <pim@ietf.org>; Fri, 30 May 2014 12:09:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13040; q=dns/txt; s=iport; t=1401476957; x=1402686557; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=PJ8h0zlanWk9A6tXTHEZTARjlufj1ISF9ShtoXDpiXE=; b=LrjeIm64gnSjxHduI6L/ZgpU+UkZ2f4sJAj1k3TZMut8NlQfrC7V4ppX 2AWqfogMlwBMetcK8Am/wJVcd7o2greVGgP2MndbQauyPS2XCOQqanfQm e+oX3BmmR1FYZG/bAv+RmNacQs09MX17s79GFRq0zrcqwW6dV0YXzCD9B k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgFAHHWiFOtJA2K/2dsb2JhbABZgwdSVQOCbLgXhzkBGXAWdIIlAQEBBAEBAQsVETEJHQEIEQQBAQECAiYCBCULFQgIAQEEARIJiDkNsi2kWReBKoxXAQEkECICAgKCb4FLBIVFlDmEMo57gzhsgQo5
X-IronPort-AV: E=Sophos;i="4.98,943,1392163200"; d="scan'208";a="48757552"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-4.cisco.com with ESMTP; 30 May 2014 19:09:16 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s4UJ9GEc007862 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 30 May 2014 19:09:16 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.164]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Fri, 30 May 2014 14:09:16 -0500
From: "Heidi Ou (hou)" <hou@cisco.com>
To: Bharat Joshi <bharat_joshi@infosys.com>, Mike McBride <mike.mcbride@ericsson.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] WGLC: draft-ietf-pim-drlb-03
Thread-Index: Ac92RKTTcHNidFXpQ2G8zQt0EgQ/KQAAWIYyARL1d4AASm8sEAAbkhIA
Date: Fri, 30 May 2014 19:09:16 +0000
Message-ID: <CFAE11B0.9D5D0%hou@cisco.com>
In-Reply-To: <35347FBF2796F94E936EE76C0E6047ED4858BD44@BLRKECMBX12.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.154.210.10]
Content-Type: text/plain; charset="utf-8"
Content-ID: <564F681486B2684A85EE01D40D10A077@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/1MK4D9yRCCZckB4f--zoYQ__cLU
Subject: Re: [pim] WGLC: draft-ietf-pim-drlb-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 30 May 2014 19:09:25 -0000

SGkgQmhhcmF0LA0KDQpJIHRyaW1tZWQgZG93biB0aGUgdGV4dCB0byBmb2N1cyBvbiB0aGUgb25l
cyBuZWVkIG1vcmUgZGlzY3Vzc2lvbi4NCg0KDQo+4oKsIEluIHNlY3Rpb24gMywgSSBkaWQgbm90
IGdldCB3aGF0ICdsb2FkIGJhbGFuY2luZycgYXJlIHdlIHRhbGtpbmcgYWJvdXQNCj5pbiBjYXNl
IG9mICdmaXJzdCBob3Agcm91dGVycyc/DQo+DQo+W2hlaWRpXSBJdCBpcyByZWZlcnJpbmcgdG8g
dGhlIGNvbW1vbiBpbXBsZW1lbnRhdGlvbiB0aGF0IHdoZW4gYQ0KPmRvd25zdHJlYW0NCj5baGVp
ZGldIHJvdXRlciBoYXMgbXVsdGlwbGUgdXBzdHJlYW0gbmVpZ2hib3JzIHRoYXQgYXJlIGVxdWFs
IGNvc3QgYXMNCj5baGVpZGldIGRldGVybWluZWQgYnkgSUdQLA0KPltoZWlkaV0gaXQgd2lsbCDC
s2xvYWQgYmFsYW5jZcKyIHRoZSBqb2lucyB3aGVuIGNob29zaW5nIGFuIHVwc3RyZWFtDQo+W2hl
aWRpXSBuZWlnaGJvci4NCj4NCj48QmhhcmF0PjogSSBzdGlsbCBkaWQgbm90IGZ1bGx5IGdldCB0
aGlzLiBJcyB0aGlzIGZvciBzb3VyY2Ugb3IgYSBSUD8NCj5Xb24ndCB0aGVyZSBiZSBtdWx0aXBs
ZSBtdWx0aWNhc3Qgc3RyZWFtIGdldCBmb3J3YXJkZWQgdG8gdGhlIExBTiBhbmQNCj50aGVuIGFz
c2VydCB3aWxsIGNob29zZSBvbmUgZm9yd2FyZGVyLiBXaHkgd291bGQgd2Ugd2FudCB0byBkbyB0
aGlzPw0KDQoNCiJsb2FkIGJhbGFuY2luZyIgZm9yIHNvdXJjZS4gV2hlbiBhIGRvd25zdHJlYW0g
c2VuZHMgUElNIEpvaW4gdG93YXJkcw0KVXBzdHJlYW0gKGluY2x1ZGluZyBGSFIpLCB0aGUgZG93
bnN0cmVhbSBsb29rcyBhdCBpdHMgdW5pY2FzdCBSSUIuIElmDQpUaGVyZSBhcmUgbXVsdGlwbGUg
RUNNUCBwYXRoIHRvIHJlYWNoIHRoZSBzb3VyY2UsIGltcGxlbWVudGF0aW9uDQpVc3VhbGx5IGRv
IGxvYWQgYmFsYW5jaW5nIGF1dG9tYXRpY2FsbHkgZm9yIGVhY2ggUklCIGxvb2t1cC4gU2F5IGlm
DQpEb3duc3RyZWFtIGhhcyBwMSxwMiwgcDMsIDMgcGF0aHMgdG8gcmVhY2ggUzEsIGl0IHdpbGwg
dXNlIHAxIGZvcg0KKFMxLEcxKSwgcDIgZm9yIChTMSxHMiksIGFuZCBQMyBmb3IgKFMxLEczKQ0K
DQoNCg0KPg0KPuKCrCBJbiBzZWN0aW9uIDMsIEkgYWxzbyBkaWQgbm90IHVuZGVyc3RhbmQgaG93
IEVDTVAgaGVscHMgaW4gdGhpcyBsb2FkDQo+YmFsYW5jaW5nLiBJZiB0aGVyZSBhcmUgbXVsdGlw
bGUgcm91dGVycyBvbiBhIExBTiBpbiB3aGljaCB0aGUgc291cmNlIGFsc28NCj5zaXRzLCBhcyBw
ZXIgUElNLCBpdHMgdGhlIERSIHdobyBpcyB0byBzZW5kIHRoZSByZWdpc3RlciBtZXNzYWdlcyB0
byB0aGUNCj5SUC4gU28gSSBhbSBub3Qgc3VyZSBob3cgRUNNUCBoZWxwcyBoZXJlIGluIG1ha2lu
ZyBvdGhlciByb3V0ZXIgb24gdGhpcw0KPkxBTiB0byBkbyB0aGlzIGluc3RlYWQgb2YgdGhlIERS
Pw0KPg0KPltoZWlkaV0gWWVzIGl0IGlzIHRoZSBEUiB0aGF0IHNlbmRzIHRoZSByZWdpc3RlcnMu
ICBCdXQgdGhlIHBhY2tldHMgYXJlDQo+W2hlaWRpXSBtb3N0bHkgZm9yd2FyZGVkIG5hdGl2ZWx5
DQo+W2hlaWRpXSBkb3duIHRoZSBzb3VyY2UgdHJlZXMgZXN0YWJsaXNoZWQgYnkgKFMsRykgam9p
bnMgZnJvbSBkb3duc3RyZWFtDQo+W2hlaWRpXSByb3V0ZXJzLg0KPg0KPjxCaGFyYXQ+OiBBcyBt
ZW50aW9uZWQgYWJvdmUsIEkgYW0gc3RpbGwgbm90IGNsZWFyIGFib3V0IHRoaXMuDQoNCg0KUGxl
YXNlIFNlZSBhYm92ZS4gDQoNCj4NCj7igqwgQXMgcGVyIFJGQyA0NjAxLCBQSU0gRFIgaXMgZWxl
Y3RlZCBmb3IgYW55IHR5cGUgb2YgbmV0d29ya3Mgc28gdGhlcmUgaXMNCj5ubyBuZWVkIHRvIG1l
bnRpb24gdGhhdCBQSU0gRFIgZWxlY3Rpb24gaXMgZG9uZSBpbiBhIG11bHRpLWFjY2VzcyBuZXR3
b3JrLg0KPg0KPltoZWlkaV0gSSBhbSBtaXNzaW5nIHRoZSB5b3VyIHBvaW50IGhlcmUuDQo+DQo+
PEJoYXJhdD46IFdoYXQgSSB3YXMgdHJ5aW5nIHRvIHN1Z2dlc3QgaXMgdGhhdCB0aGlzIGRyYWZ0
IGRvZXMgbm90IG5lZWQNCj50byBtZW50aW9uIHRoYXQgYSBEUiBlbGVjdGlvbiBpcyBkb25lIGlu
IG11bHRpLWFjY2VzcyBuZXR3b3JrLiBJdCBjYW4NCj5qdXN0IHJlZmVyIHRvIFJGQyA0NjAxLg0K
DQoNCiJtdWx0aS1hY2Nlc3MiIG1lbnRpb25lZCBoZXJlLCBtYWlubHkgZm9yIGRlc2NyaWJpbmcg
dGhlIHNjZW5hcmlvIHRoZQ0KZHJhZnQgaXMgdGFyZ2V0aW5nIGZvci4NCkl0IHdvdWxkIGJlIGVh
c3kgZm9yIHJlYWRlcnMgdG8gcGljdHVyZSBpdC4NCg0KPg0KPuKCrCBJbiBzZWN0aW9uIDQsIGlu
IHNlbnRlbmNlICJUaGUgUElNIERSIGlzIHJlc3BvbnNpYmxlIGZvciBzZW5kaW5nDQo+Sm9pbi9Q
cnVuZSBtZXNzYWdlcyB0byB0aGUgUlAgb3Igc291cmNlLiIsIEkgdGhpbmsgd2Ugc2hvdWxkIG1l
bnRpb24gdGhhdA0KPnRoaXMgaXMgZG9uZSBmb3IgdGhlIGxvY2FsIGhvc3QncyBqb2luL2xlYXZl
Lg0KPg0KPltoZWlkaV0gVGhhdCB3b3VsZCBiZSByZWR1bmRhbnQuIElmIGl0IGlzIG5vdCBmb3Ig
bG9jYWwgaG9zdHMsIHRoZW4gaXQNCj5baGVpZGldIGRvZXNuwrl0IG1hdHRlciB3aGV0aGVyIHRo
ZSByb3V0ZXIgaXMgYSBEUiBvciBub3Qgb24gdGhlIGludGVyZmFjZQ0KPltoZWlkaV0gZnJvbSB3
aGljaCBhIFBJTSBKb2luL1BydW5lIGlzIHJlY2VpdmVkLg0KPg0KPjxCaGFyYXQ+OiBFeGFjdGx5
LCBhIERSIHJvdXRlciBtYXkgb3IgbWF5IG5vdCBzZW5kIFBJTSBqb2luL3BydW5lIHRvIFJQDQo+
YmVjYXVzZSB0aGF0IHdpbGwgZGVwZW5kIHVwb24gd2hldGhlciBEUiBpcyB0aGUgdXBzdHJlYW0g
cm91dGVyIG9yIG5vdC4NCj5CdXQgaW4gY2FzZSBvZiBsb2NhbCBqb2lucywgRFIgaGFzIHRoZSBy
ZXNwb25zaWJpbGl0eSB0byBkbyBpdCBhbmQgaGVuY2UNCj50byBtYWtlIHRoZSBhYm92ZSBzdGF0
ZW1lbnQgY29tcGxldGUsIGl0IHdpbGwgYmUgYmV0dGVyIHRvIGFkZCB0aGF0IHRoaXMNCj5pcyBm
b3IgbG9jYWwgam9pbnMuDQoNCg0KT2ssIGFkZGVkICJsb2NhbCBqb2luIi4NCg0KDQo+DQo+DQo+
4oKsIEluIHNlY3Rpb24gNC4zLCBpdHMgbm90IGNsZWFyIHdoYXQgd2lsbCBiZSB0aGUgY29udGVu
dHMgb2YgZmlyc3QgUElNDQo+aGVsbG8gbWVzc2FnZSBvZiBhIHJvdXRlciBjb21pbmcgdXA/IFdp
bGwgaXQgY29udGFpbiBMQiBHRFIgb3B0aW9uIG9yIG5vdD8NCj5BdCB0aGF0IHRpbWUsIGl0IG1h
eSBub3Qga25vdyB3aGV0aGVyIGl0cyBhIERSIG9yIG5vdC4gQWN0dWFsbHksIGl0IHdpbGwNCj5h
c3N1bWUgdGhhdCBpdHMgdGhlIERSIHVudGlsIGl0IHJlY2VpdmVzIGEgaGVsbG8gbWVzc2FnZSBm
cm9tIGEgaGlnaGVyIERSDQo+cHJpb3JpdHkgcm91dGVyLg0KPg0KPg0KPltoZWlkaV0gSXQgZGVw
ZW5kcyBvbiB0aGUgaW1wbGVtZW50YXRpb27CuXMgY2hvaWNlIHdoZXRoZXIgaXQgY29uc2lkZXJz
DQo+W2hlaWRpXSBpdHNlbGYgYXMgYSBEUiB3aGVuIHRoZSBpbnRlcmZhY2UgY29tZXMgdXAuDQo+
W2hlaWRpXSBUaGUgZHJhZnQgZG9lc27CuXQgaW50ZW5kIHRvIGRpY3RhdGUgdGhhdCBjaG9pY2Uu
IElUIGp1c3Qgc3BlY2lmaWVzDQo+W2hlaWRpXSB3aGF0IHRvIHNlbmQuDQo+DQo+PEJoYXJhdD46
IEJ1dCB3b3VsZCBpdCBjcmVhdGUgYW55IGludGVyb3BlcmFiaWxpdHkgaXNzdWU/IElmIG9uZSBy
b3V0ZXINCj5hc3N1bWVzIHRoYXQgaXQgbXVzdCBjb21lIGluIHRoZSBmaXJzdCBQSU0gbWVzc2Fn
ZSBhbmQgYW5vdGhlciBkb2VzIG5vdA0KPnNlbmQgaXQgaW4gZmlyc3QgUElNIG1lc3NhZ2UuDQoN
Cg0KSWYgYSByb3V0ZXIgYXNzdW1lIGl0cyBEUiwgaXQgc2hvdWxkIHNlbmQgb3V0IHRoZSBuZXcg
R0RSIG9wdGlvbi4NCg0KDQoNCj7igqwgSW4gc2VjdGlvbiA2LjMsIGluIGNhc2Ugb2YgUElNIGFz
c2VydCwgc2hvdWxkIG5vdCB3ZSBvdmVycmlkZSB0aGUNCj5leGlzdGluZyBBc3NlcnQgYWxnb3Jp
dGhtIGNvbXBsZXRlbHkgYW5kIHN1Z2dlc3QgdGhhdCB0aGUgd2lubmVyIHNob3VsZCBiZQ0KPnNl
bGVjdGVkIGJhc2VkIG9uIHRoZSBjdXJyZW50bHkgc2VsZWN0ZWQgR0RSPw0KPg0KPltoZWlkaV0g
Q291bGQgeW91IHBsZWFzZSBlbGFib3JhdGUgdGhlIHJlYXNvbnMgd2h5IDYuMyBpcyBpbnN1ZmZp
Y2llbnQgaW4NCj5baGVpZGldIHRoaXMgY2FzZT8NCj4NCj48QmhhcmF0PjogV2hhdCBJIHdhcyB0
cnlpbmcgdG8gYXNrIGlzIHRoYXQgaXMgdGhlcmUgcmVhbGx5IGEgbmVlZCB0bw0KPnN1Z2dlc3Qg
bW9kaWZpY2F0aW9ucyBpbiBhc3NlcnQgbWVjaGFuaXNtLiBJbnN0ZWFkLCBsZXQgdGhlIGFzc2Vy
dA0KPm1lY2hhbmlzbSB1c2UgdGhlIGV4aXN0aW5nIGFsZ29yaXRobSBhcyBpdCBpcy4gVGhlIG9u
bHkgdGhpbmcgd2UgbmVlZCBpcw0KPnRoYXQgd2Ugd291bGQgd2FudCB0byByZWR1Y2UgdGhlIHRy
YWZmaWMgbG9zcyB3aGljaCBjYW4gYmUgYXZvaWRlZCBieQ0KPm1ha2luZyBSMSBhbmQgUjIgbm90
IHN0b3BwaW5nIHRoZSBmb3J3YXJkaW5nLg0KDQoNCkJ1dCB3ZSBhcmUgdHJ5aW5nIHRvIGZvcndh
cmQgdHJhZmZpYyB2aWEgR0RSLCBhbmQgdGhhdCBjYW4ndCBiZSBkb25lIGJ5DQpjdXJyZW50IEFz
c2VydCBhbGdvcml0aG0uDQoNCgkNCg0KDQo+DQo+PEJoYXJhdD46IEFsc28sIEkgd2FzIGp1c3Qg
cmVhZGluZyB0aGUgdGV4dCBpbiB0aGlzIHNlY3Rpb24gaW4gdmVyc2lvbg0KPjAzLiBJIHRoaW5r
IHRoZXJlIGlzIGEgc21hbGwgdHlwbyBpbg0KPjxCaGFyYXQ+OiAiV2hlbiBSMyBjb21lcyB1cCBv
bmxpbmUsIGl0IGlzIHBvc3NpYmxlIHRoYXQgUjMgYmVjb21lcyBHRFINCj5mb3IgYm90aCBHMSBh
bmQgRzIsIGhlbmNlDQo+PEJoYXJhdD46IFIyIHN0YXJ0cyB0byBidWlsZCB0aGUgZm9yd2FyZGlu
ZyB0cmVlIGZvciBHMSBhbmQgRzIiDQo+PEJoYXJhdD46IEkgdGhpbmsgaXQgc2hvdWxkIHNheSAi
UjMgc3RhcnRzIHRvIGJ1aWxkIi4NCg0KCUNvcnJlY3RlZC4gVGhhbmtzLg0KDQoNCg0KLSBIZWlk
aQ0KDQoNCg0KPg0KPg0KPk9uIDUvMjIvMTQgMTA6MTcgUE0sICJCaGFyYXQgSm9zaGkiIDxiaGFy
YXRfam9zaGlAaW5mb3N5cy5jb20+IHdyb3RlOg0KPg0KPj5NaWtlLCBBdXRob3JzLA0KPj4NCj4+
ICAgICAgIEkgaGFkIHNlbnQgc29tZSBxdWVzdGlvbnMvc3VnZ2VzdGlvbnMgb24gdGhpcyBkcmFm
dCBhbG1vc3QgYSB5ZWFyDQo+PmJhY2suDQo+Pg0KPj4gICAgICAgSGVyZSBpcyB0aGUgbGluazoN
Cj4+aHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL3BpbS9jdXJyZW50L21zZzAy
NzIwLmh0bWwNCj4+DQo+PiAgICAgICBJIGFtIG5vdCBzdXJlIGlmIEkgbWlzc2VkIHRoZSByZXNw
b25zZS4gSSBhbSBhbHNvIG5vdCBzdXJlIGlmDQo+PnRoZXNlIGhhcyBiZWVuIGFkZHJlc3NlcyBp
biB0aGUgbmV3IHJldmlzaW9uLg0KPj4NCj4+UmVnYXJkcywNCj4+QmhhcmF0IEpvc2hpDQo+Pmh0
dHA6Ly9iaXRlLXRoZS1ieXRlcy5ibG9nc3BvdC5jb20vDQo+Pl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4+RnJvbTogcGltIFtwaW0tYm91bmNlc0BpZXRmLm9yZ10g
b24gYmVoYWxmIG9mIE1pa2UgTWNCcmlkZQ0KPj5bbWlrZS5tY2JyaWRlQGVyaWNzc29uLmNvbV0N
Cj4+U2VudDogRnJpZGF5LCBNYXkgMjMsIDIwMTQgMTA6NDAgQU0NCj4+VG86IHBpbUBpZXRmLm9y
Zw0KPj5TdWJqZWN0OiBbcGltXSBXR0xDOiBkcmFmdC1pZXRmLXBpbS1kcmxiLTAzDQo+Pg0KPj5T
dGlnIGFuZCBJIGZlZWwgZHJhZnQtaWV0Zi1waW0tZHJsYi0wMyBpcyByZWFkeSBmb3IgV0dMQy4g
VGhlIGF1dGhvcnMNCj4+aGF2ZSBhZGRyZXNzZWQgYWxsIGNvbW1lbnRzIHRvIGRhdGUuIFRvZGF5
IHN0YXJ0cyBhIHR3byB3ZWVrIFdHTEMsIHBsZWFzZQ0KPj5zcGVhayB1cCBlaXRoZXIgd2F5Lg0K
Pj4NCj4+aHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLXBpbS1kcmxiLTAzLnR4dA0K
Pj4NCj4+dGhhbmtzLA0KPj5taWtlDQo+Pg0KPj5fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPj5waW0gbWFpbGluZyBsaXN0DQo+PnBpbUBpZXRmLm9yZw0K
Pj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbQ0KPj4NCj4+KioqKioq
KioqKioqKioqKiBDQVVUSU9OIC0gRGlzY2xhaW1lciAqKioqKioqKioqKioqKioqKg0KPj5UaGlz
IGUtbWFpbCBjb250YWlucyBQUklWSUxFR0VEIEFORCBDT05GSURFTlRJQUwgSU5GT1JNQVRJT04g
aW50ZW5kZWQNCj4+c29sZWx5DQo+PmZvciB0aGUgdXNlIG9mIHRoZSBhZGRyZXNzZWUocykuIElm
IHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsDQo+PnBsZWFzZQ0KPj5ub3RpZnkg
dGhlIHNlbmRlciBieSBlLW1haWwgYW5kIGRlbGV0ZSB0aGUgb3JpZ2luYWwgbWVzc2FnZS4gRnVy
dGhlciwgeW91DQo+PmFyZSBub3QNCj4+dG8gY29weSwgZGlzY2xvc2UsIG9yIGRpc3RyaWJ1dGUg
dGhpcyBlLW1haWwgb3IgaXRzIGNvbnRlbnRzIHRvIGFueSBvdGhlcg0KPj5wZXJzb24gYW5kDQo+
PmFueSBzdWNoIGFjdGlvbnMgYXJlIHVubGF3ZnVsLiBUaGlzIGUtbWFpbCBtYXkgY29udGFpbiB2
aXJ1c2VzLiBJbmZvc3lzDQo+PmhhcyB0YWtlbg0KPj5ldmVyeSByZWFzb25hYmxlIHByZWNhdXRp
b24gdG8gbWluaW1pemUgdGhpcyByaXNrLCBidXQgaXMgbm90IGxpYWJsZSBmb3INCj4+YW55IGRh
bWFnZQ0KPj55b3UgbWF5IHN1c3RhaW4gYXMgYSByZXN1bHQgb2YgYW55IHZpcnVzIGluIHRoaXMg
ZS1tYWlsLiBZb3Ugc2hvdWxkIGNhcnJ5DQo+Pm91dCB5b3VyDQo+Pm93biB2aXJ1cyBjaGVja3Mg
YmVmb3JlIG9wZW5pbmcgdGhlIGUtbWFpbCBvciBhdHRhY2htZW50LiBJbmZvc3lzDQo+PnJlc2Vy
dmVzIHRoZQ0KPj5yaWdodCB0byBtb25pdG9yIGFuZCByZXZpZXcgdGhlIGNvbnRlbnQgb2YgYWxs
IG1lc3NhZ2VzIHNlbnQgdG8gb3IgZnJvbQ0KPj50aGlzIGUtbWFpbA0KPj5hZGRyZXNzLiBNZXNz
YWdlcyBzZW50IHRvIG9yIGZyb20gdGhpcyBlLW1haWwgYWRkcmVzcyBtYXkgYmUgc3RvcmVkIG9u
DQo+PnRoZQ0KPj5JbmZvc3lzIGUtbWFpbCBzeXN0ZW0uDQo+PioqKklORk9TWVMqKioqKioqKiBF
bmQgb2YgRGlzY2xhaW1lciAqKioqKioqKklORk9TWVMqKioNCj4+DQo+Pl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PnBpbSBtYWlsaW5nIGxpc3QNCj4+
cGltQGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGlt
DQo+DQo+DQo+DQo+DQo+DQo+T24gNS8yMi8xNCAxMDoxNyBQTSwgIkJoYXJhdCBKb3NoaSIgPGJo
YXJhdF9qb3NoaUBpbmZvc3lzLmNvbT4gd3JvdGU6DQo+DQo+Pk1pa2UsIEF1dGhvcnMsDQo+Pg0K
Pj4gICAgICAgSSBoYWQgc2VudCBzb21lIHF1ZXN0aW9ucy9zdWdnZXN0aW9ucyBvbiB0aGlzIGRy
YWZ0IGFsbW9zdCBhIHllYXINCj4+YmFjay4NCj4+DQo+PiAgICAgICBIZXJlIGlzIHRoZSBsaW5r
Og0KPj5odHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvcGltL2N1cnJlbnQvbXNn
MDI3MjAuaHRtbA0KPj4NCj4+ICAgICAgIEkgYW0gbm90IHN1cmUgaWYgSSBtaXNzZWQgdGhlIHJl
c3BvbnNlLiBJIGFtIGFsc28gbm90IHN1cmUgaWYNCj4+dGhlc2UgaGFzIGJlZW4gYWRkcmVzc2Vz
IGluIHRoZSBuZXcgcmV2aXNpb24uDQo+Pg0KPj5SZWdhcmRzLA0KPj5CaGFyYXQgSm9zaGkNCj4+
aHR0cDovL2JpdGUtdGhlLWJ5dGVzLmJsb2dzcG90LmNvbS8NCj4+X19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPj5Gcm9tOiBwaW0gW3BpbS1ib3VuY2VzQGlldGYub3Jn
XSBvbiBiZWhhbGYgb2YgTWlrZSBNY0JyaWRlDQo+PlttaWtlLm1jYnJpZGVAZXJpY3Nzb24uY29t
XQ0KPj5TZW50OiBGcmlkYXksIE1heSAyMywgMjAxNCAxMDo0MCBBTQ0KPj5UbzogcGltQGlldGYu
b3JnDQo+PlN1YmplY3Q6IFtwaW1dIFdHTEM6IGRyYWZ0LWlldGYtcGltLWRybGItMDMNCj4+DQo+
PlN0aWcgYW5kIEkgZmVlbCBkcmFmdC1pZXRmLXBpbS1kcmxiLTAzIGlzIHJlYWR5IGZvciBXR0xD
LiBUaGUgYXV0aG9ycw0KPj5oYXZlIGFkZHJlc3NlZCBhbGwgY29tbWVudHMgdG8gZGF0ZS4gVG9k
YXkgc3RhcnRzIGEgdHdvIHdlZWsgV0dMQywgcGxlYXNlDQo+PnNwZWFrIHVwIGVpdGhlciB3YXku
DQo+Pg0KPj5odHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWlldGYtcGltLWRybGItMDMudHh0
DQo+Pg0KPj50aGFua3MsDQo+Pm1pa2UNCj4+DQo+Pl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+PnBpbSBtYWlsaW5nIGxpc3QNCj4+cGltQGlldGYub3Jn
DQo+Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGltDQo+Pg0KPj4qKioq
KioqKioqKioqKioqIENBVVRJT04gLSBEaXNjbGFpbWVyICoqKioqKioqKioqKioqKioqDQo+PlRo
aXMgZS1tYWlsIGNvbnRhaW5zIFBSSVZJTEVHRUQgQU5EIENPTkZJREVOVElBTCBJTkZPUk1BVElP
TiBpbnRlbmRlZA0KPj5zb2xlbHkNCj4+Zm9yIHRoZSB1c2Ugb2YgdGhlIGFkZHJlc3NlZShzKS4g
SWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwNCj4+cGxlYXNlDQo+Pm5vdGlm
eSB0aGUgc2VuZGVyIGJ5IGUtbWFpbCBhbmQgZGVsZXRlIHRoZSBvcmlnaW5hbCBtZXNzYWdlLiBG
dXJ0aGVyLCB5b3UNCj4+YXJlIG5vdA0KPj50byBjb3B5LCBkaXNjbG9zZSwgb3IgZGlzdHJpYnV0
ZSB0aGlzIGUtbWFpbCBvciBpdHMgY29udGVudHMgdG8gYW55IG90aGVyDQo+PnBlcnNvbiBhbmQN
Cj4+YW55IHN1Y2ggYWN0aW9ucyBhcmUgdW5sYXdmdWwuIFRoaXMgZS1tYWlsIG1heSBjb250YWlu
IHZpcnVzZXMuIEluZm9zeXMNCj4+aGFzIHRha2VuDQo+PmV2ZXJ5IHJlYXNvbmFibGUgcHJlY2F1
dGlvbiB0byBtaW5pbWl6ZSB0aGlzIHJpc2ssIGJ1dCBpcyBub3QgbGlhYmxlIGZvcg0KPj5hbnkg
ZGFtYWdlDQo+PnlvdSBtYXkgc3VzdGFpbiBhcyBhIHJlc3VsdCBvZiBhbnkgdmlydXMgaW4gdGhp
cyBlLW1haWwuIFlvdSBzaG91bGQgY2FycnkNCj4+b3V0IHlvdXINCj4+b3duIHZpcnVzIGNoZWNr
cyBiZWZvcmUgb3BlbmluZyB0aGUgZS1tYWlsIG9yIGF0dGFjaG1lbnQuIEluZm9zeXMNCj4+cmVz
ZXJ2ZXMgdGhlDQo+PnJpZ2h0IHRvIG1vbml0b3IgYW5kIHJldmlldyB0aGUgY29udGVudCBvZiBh
bGwgbWVzc2FnZXMgc2VudCB0byBvciBmcm9tDQo+PnRoaXMgZS1tYWlsDQo+PmFkZHJlc3MuIE1l
c3NhZ2VzIHNlbnQgdG8gb3IgZnJvbSB0aGlzIGUtbWFpbCBhZGRyZXNzIG1heSBiZSBzdG9yZWQg
b24NCj4+dGhlDQo+PkluZm9zeXMgZS1tYWlsIHN5c3RlbS4NCj4+KioqSU5GT1NZUyoqKioqKioq
IEVuZCBvZiBEaXNjbGFpbWVyICoqKioqKioqSU5GT1NZUyoqKg0KPj4NCj4+X19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+cGltIG1haWxpbmcgbGlzdA0K
Pj5waW1AaWV0Zi5vcmcNCj4+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9w
aW0NCj4NCg0K


From nobody Fri May 30 23:44:52 2014
Return-Path: <sami.biz.email@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E13F1A07A8 for <pim@ietfa.amsl.com>; Fri, 30 May 2014 23:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 X936orGuigdm for <pim@ietfa.amsl.com>; Fri, 30 May 2014 23:44:49 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A0E41A07A1 for <pim@ietf.org>; Fri, 30 May 2014 23:44:48 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id hi2so2216815wib.7 for <pim@ietf.org>; Fri, 30 May 2014 23:44:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding; bh=uNAucD2m2OAbRwvtWNTwL9rrr2MH357XlSyXM0AWheE=; b=A3Ld0SGG6JNga6Fa3y+BdKJPkEWl/sS/S8MPjBtI7vLT5mUhJgv2TBMftnNWN9dMvB jNw3kp/jVujTzWqPd+hlyO/tnAuvj1xtWHObOr8c9GrHeZTOt+nIVcZJ/iaUSiesec9C rE2OqtPpVfTPlJYz2WhRwPKRIhphJGfWHAXg4OU/ICwPVKwM2eTYunfXl9T1ZLwjGjYD d9i89OcCAFK/VU2IDtb9BNzUMph5ka956UI6rHVWdaFwj2staNBOH6fV213gSsKGlYzh oINsozTydxImj23+ryn10vtNNcP0jjOUfwIuoAaPa4BMvftPoNgoHLACTdz3uIKzCg+q sQVQ==
X-Received: by 10.194.82.170 with SMTP id j10mr29602269wjy.63.1401518683194; Fri, 30 May 2014 23:44:43 -0700 (PDT)
Received: from [192.168.1.5] ([178.253.51.128]) by mx.google.com with ESMTPSA id m1sm12193441wib.20.2014.05.30.23.44.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 May 2014 23:44:42 -0700 (PDT)
Message-ID: <53898767.7020104@gmail.com>
Date: Sat, 31 May 2014 11:10:23 +0330
From: saeed sami <sami.biz.email@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: pim@ietf.org, pim-chairs@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/ukTRcRd-KrLeeLTyhXeCRwRfqzk
Subject: [pim] new version submitted draft-sami-pim-ng-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 31 May 2014 06:44:51 -0000

A new version of draft-sami-pim-ng is submitted and can be reached at :
https://datatracker.ietf.org/doc/draft-sami-pim-ng/
  http://www.ietf.org/internet-drafts/draft-sami-pim-ng-03.txt

It is edited  and 3 sections are added which are related to :
1- preventing the possible delay in source discovery.
2-loop prevention
3-DR election and pim Assert message , and since the current best practice is the processes defined by PIM-SM it is not changed except for a DR at edge of a multi-access network in a PIM-NG multicast domain.

I would like to thank Stig Venaas for his kind review and comments up to this point which have been so helpful.
Your reviews and comments are most appreciated. and I hope to read the
comments of PIM working group experts soon.

Abstract:
    This document specifies protocol independent multicast- Next
    generation or simply called PIM-NG. like PIM-SM, PIM-NG uses the
    underlying unicast routing information, but unlike PIM-SM it doesn't
    necessarily need to build unidirectional shared trees rooted at a
    Rendezvous Point (RP) per group, due to the fact that the processes
    through which a source registers with the Rendezvous Point and a host
    finds the source of the multicast destination groups it needs are
    done in a whole new way. So at some points PIM-NG works faster than
    its predecessor. Also the new Domain concept, unique to PIM-NG, along
    the RPF check method used in PIM-NG specifications provides many
    features along a robust and flexible control and administration over
    multicast networks.

Sincerely
Saeed Sami

