
From asaeda@sfc.wide.ad.jp  Thu May  2 01:56:43 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E5E21F98C8 for <pim@ietfa.amsl.com>; Thu,  2 May 2013 01:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nAcRw1bBQN1w for <pim@ietfa.amsl.com>; Thu,  2 May 2013 01:56:42 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id D359821F96B5 for <pim@ietf.org>; Thu,  2 May 2013 01:55:36 -0700 (PDT)
Received: from localhost (unknown [133.69.32.86]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 8171127809C; Thu,  2 May 2013 17:55:33 +0900 (JST)
Date: Thu, 02 May 2013 17:55:36 +0900 (JST)
Message-Id: <20130502.175536.137418002.asaeda@sfc.wide.ad.jp>
To: bharat_joshi@infosys.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <35347FBF2796F94E936EE76C0E6047ED32E39BD4@BLRKECMBX13.ad.infosys.com>
References: <5175B9DB.3020403@venaas.com> <51796AF5.6040702@venaas.com> <35347FBF2796F94E936EE76C0E6047ED32E39BD4@BLRKECMBX13.ad.infosys.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 02 May 2013 08:56:43 -0000

Hi Bharat,

Thanks for your review.

> 1. In Abstract, can we remove the usage of 'fast leave' and just
> keep 'shortening leave latency'. A quick google search on 'fast
> leave' shows that it is a known term in the context of IGMPv2 where
> a router does not send the group specific query and stops forwarding
> multicast traffic for the group on that interface. As here 'fast
> leave' is not referring to a similar behavior, I suggest to use
> 'shortening leave latency' instead.

Fast leave itself is a general terminology. It does not specific only
for the IGMPv2's procedure. For example, see rfc3810 (MLDv2).

> 2. In second para of section 1, can we also mention that to avoid
> loss of unsolicited reports, each unsolicited report is sent out at
> least robustness count times. After this, we can talk about queries
> as mentioned in this para.

Ok, I'll add the sentense.

> 3. In third par of section 1, first sentence seems complex to me.
> 
> Multicast routers are capable of periodically maintaining the
> multicast membership state of downstream hosts attached to the same
> link by acquiring unsolicited report messages and synchronizing the
> actual membership state within the General Query timer interval
> (i.e., [Query Interval] value defined in [1][2].) 
> 
> Can we reword the above to as mentioned below or something on these lines:
> 
> Multicast routers learn multicast membership state of 
> downstream hosts by unsolicited report messages. Multicast
> routers send periodic queries to keep the membership state
> synchronized by solicited report messages.

Ok, I'll simplify the sentence to the following;

   Multicast routers send periodic queries within the General Query
   timer interval (i.e., [Query Interval] value defined in [1][2]) to
   keep the membership state up to date.

> 4. As its mentioned that 'explicit tracking function does not
> guarantee that the membership state will always be perfectly
> synchronized', should the task 'Per-host accounting' using this
> function be really done? It may give incorrect results and to some
> providers, accounting is very important. Right?

Although the explicit tracking function will contribute to accounting,
it is not the scope of this draft. It is just a use case.

In fact, in the previous version, we said something like,

   "where this document mainly focuses on the above first and second
   bullets in the following sections."

in the same paragraph, but removed as it's obvious. If it's better to
mention it, I'll move it back again.

Or shall I remove the third and fourth lines? I don't mind either.

> 5. Can you please elaborate on 'Maintaining multicast channel
> characteristics'? What channel characteristics we are referring
> here? Also how does explicit tracking function helps in this?

It is not the scope of this document, too. It is one of the use cases
as well.

While I wrote these two lines to show the potential use cases of this
function, if just removing these two lines is preferable, I'll remove
it.

(But if no strong opinion, I prefer to keep these use cases as is with
the above "where" clause. Opinion?)

> 6. In section 3.1, I did not get the need of "If there are no more
>    receivers maintained,
>    the router may keep the membership state information with an empty
>    receiver list.". Does this for any specific purpose? If so, can
>    we add this in the draft.

Allocating memory for membership state information is a cost. But I
agree removing this sentence is reasonable as it is an implementation
specific issue.

> 7. Should not 'Membership State Information' be deleted when the
> corresponding multicast channel times out in the router? The router
> should not be maintaining this multicast channel state information
> forever. For example: if the last hosts who had joined a channel
> goes down without sending a leave request.

It's up to the implementation as above. I'll remove such
implementation dependent statement.

> 8. In section 3.2, in first sentence,
> 
> In accordance with [1] and [2], whenever a router receives the State-
> Change Report, it sends the corresponding Group-Specific or Group-
> and-Source Specific Query messages to confirm whether or not the
> report sender is the sole member host.
> 
> Can we reword the above because router does not always send
> Group-Specific or Group-and-Source Specific Query messages whenever
> it receives a State-Change Report? We can reword it to:
> 
> In accordance with [1] and [2], whenever a router receives the State-
> Change Report, it might send the corresponding Group-Specific or Group-
> and-Source Specific Query messages to confirm whether or not the
> report sender was the sole member host.

No. The original sentence is correct. That behevior is defined in [1]
and [2] as the standard behavior (without the explicit tracking
function enabled).

> Please also note the change of 'is' to 'was' in the last part of the sentence.
> 
> 9. In section 3.2, in para 3, "This is in order to confirm whether
> or not the host is the sole member."
> -> "This is in order to confirm whether or not the host was the sole member."

I don't think "is" is wrong.

> 10. In section 3.3, second para, what I infer from the first
> sentence is that router prunes the channel after LMQI and LLQI. This
> does not look correct. Later in the same para, last sentence correct
> this by mentioning LMQT and LLQT is the total time router wait after
> the first query is sent, to prune the channel. Can we fix the first
> sentence here?

Ok, I'll remove the sentence, "before the router prunes the channel
from the network", for LMQI/LLQI explanation.

> 11. A similar issue exist when LMQC and LLQC is explained in the above para.

I don't think so, because this sentence comes from rfc3810.

> 12. Last para of section 3.3 tries to describe how a lower values of
> LMQI/LMQC then the default suggested, can shorten the leave
> latency. But it does not clearly articulate how explicit tracking
> function helps if the two parameters are configured to the lower
> values. Can we add some details on that here?

LMQI/LLQI are the standard values defined in rfc3376 and 3810. All the
details and configurations are mentioned in them, and I believe
repeating these descriptions in this document wouldn't be needed.

> 13. In section 4, in 3rd para, in following sentence:
> 
> The second case occurs when a router sends a specific query but does
> not receive a State-Change Report from a downstream host within an
> LMQT or LLQT period.
> 
> I think when a host receives specific query, it generates a current-state
> report. Right?

Right.
As the document says "membership expectation will be inconsistent due
to an outdated membership state", this section describes the situation
in which report messages sent by downstream members are not reached to
the router due to some trouble.

> 14. As host membership protocols are unreliable, there will always
> be a possibility of outdated membership state as packets may get
> lost. I am not sure how does explicit tracking function lowers this
> possibility.

This document does not say that the explicit tracking function lowers
that possibility. This section discusses how to lower the possibility.
If people misunderstand the point, I'll clearly say,
    Regardless whether the explicit tracking function is enabled or
    not, there are possibilities that a router's membership
    expectation is inconsistent due to an outdated membership state.
at the beginning of this section.

> 15. In section 4, last para seems to explain how to fix the outdated
> membership state that is introduced because of explicit tracking
> function in a router while the section header seems to suggest that
> explicit tracking function can lower the possibility of outdated
> membership state.

No, as I said above, this document does not say that the explicit
tracking function lowers that possibility.

> 16. In section 5, in first para, we established that a MLD report
> received with unspecified source address is discarded then in second
> para, we mention that no membership-state information is created for
> such a request. So should we reword this to talk about only IGMP
> case here.

I agree. I'll remove the case of using MLD's unspecified address.

> 17. In section 6, in first para, its mentioned that explicit
> tracking does not work with older version of protocol. If I am not
> mistaken, fast/immediate leave implemented by some vendors do
> explicit tracking of the host. While I agree that hosts does report
> suppression but that happens only in case its a solicited
> report. First few (robustness count) unsolicited reports are usually
> enough to track the host.

I don't deny a router only speaks the older version protocols can
track the membership state only with unsolicited reports, but it has
more risk for the router to have the outdated membership state as it
cannot confirm the state with solicited reports.
Moreover, switching the tracking mechanism "only with uncolicited
reports (i.e. older version)" to "both with solicited and unsolicited
reports (i.e. current version)" would give complexities.
Therefore I proposed to disable the function in the older version's
router.

BTW, this document does not prohibit to keep enabling the explicit
tracking function in the older version's router, as it says "SHOULD
disable", not "MUST disable". But if people prefer "MAY disable", I'd
change "SHOULD" to "MAY" for it. Opinion?

> 18. In section 6, should not we talk about how the membership state
> information is deleted when the version is lowered and the channel
> is no more required.

Do you mean the following "MAY NOT" is not suitable for this document
as it's implementation dependent?
"the router MAY NOT flush the maintained membership state information"
If so, I could agree. I'll change "MAY NOT" to "may not".

> 19. If we can assume that the robustness count configured in a
> router truly represents the robustness of that network and if a
> packet is sent this many times, the intended destination will
> receive the packet at least once, this whole draft can be simplified
> a lot. There is no need to generate group or group-source specific
> queries even when all the hosts have left that channel. I am sure
> there is something I have missed because this is how fast/immediate
> leave is implemented for older version of protocols.

I tend to agree, but such protocol tuning is beyond the scope of this
document.
Also, we had discussions about specific query suppression in the
meetings several times. Our consensus was that the specific query
suppression should be the option (i.e. saying "SHOULD disable this
specific query suppression" as you see in section 3.2).

Thank you.

Regards,
--
Hitoshi Asaeda

From bharat_joshi@infosys.com  Thu May  2 07:52:34 2013
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C937C21F8C30 for <pim@ietfa.amsl.com>; Thu,  2 May 2013 07:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F6jsLLm+u0FM for <pim@ietfa.amsl.com>; Thu,  2 May 2013 07:52:27 -0700 (PDT)
Received: from KECGATE08.infosys.com (kecgate08.infosys.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id 69D2221F8CA0 for <pim@ietf.org>; Thu,  2 May 2013 07:52:23 -0700 (PDT)
X-TM-IMSS-Message-ID: <48fed46e000a5726@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 48fed46e000a5726 ; Thu, 2 May 2013 20:28:54 +0530
Received: from BLRKECHUB10.ad.infosys.com (10.66.236.120) by blrkechub01.ad.infosys.com (10.66.236.41) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 2 May 2013 20:21:39 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by blrkechub10.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Thu, 2 May 2013 20:22:12 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
Thread-Topic: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
Thread-Index: AQHOQduqGQSf6F+FGk6WsRG8zxIhsJjufku8gALHaQCAAHXTcg==
Date: Thu, 2 May 2013 14:52:12 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED32E3A122@BLRKECMBX13.ad.infosys.com>
References: <5175B9DB.3020403@venaas.com>	<51796AF5.6040702@venaas.com> <35347FBF2796F94E936EE76C0E6047ED32E39BD4@BLRKECMBX13.ad.infosys.com>, <20130502.175536.137418002.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130502.175536.137418002.asaeda@sfc.wide.ad.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.37.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 02 May 2013 14:52:34 -0000

Hi Hitoshi,

    Thanks for your response. Please see my replies in line for few point=
s.

Regards,
Bharat

> 
> Thanks for your review.
> 
> > 1. In Abstract, can we remove the usage of 'fast leave' and just
> > keep 'shortening leave latency'. A quick google search on 'fast
> > leave' shows that it is a known term in the context of IGMPv2 where
> > a router does not send the group specific query and stops forwarding
> > multicast traffic for the group on that interface. As here 'fast
> > leave' is not referring to a similar behavior, I suggest to use
> > 'shortening leave latency' instead.
> 
> Fast leave itself is a general terminology. It does not specific only
> for the IGMPv2's procedure. For example, see rfc3810 (MLDv2).

RFC 3810 defines a normal leave in IGMP term as fast leave. I am not sure=
 why that term was used in MLDv2 RFC. If someone on the list knows, I wou=
ld want to know.

As this draft talks about both IGMP/MLD, and as 'Fast leave' is known as =
two different things in IGMP and MLD, to keep abstract protocol independe=
nt, I would suggest to not use 'Fast leave' in this draft.

> > 2. In second para of section 1, can we also mention that to avoid
> > loss of unsolicited reports, each unsolicited report is sent out at
> > least robustness count times. After this, we can talk about queries
> > as mentioned in this para.
> 
> Ok, I'll add the sentense.

Ok.

> > 3. In third par of section 1, first sentence seems complex to me.
> >
> > Multicast routers are capable of periodically maintaining the
> > multicast membership state of downstream hosts attached to the same
> > link by acquiring unsolicited report messages and synchronizing the
> > actual membership state within the General Query timer interval
> > (i.e., [Query Interval] value defined in [1][2].)
> >
> > Can we reword the above to as mentioned below or something on these
> lines:
> >
> > Multicast routers learn multicast membership state of
> > downstream hosts by unsolicited report messages. Multicast
> > routers send periodic queries to keep the membership state
> > synchronized by solicited report messages.
> 
> Ok, I'll simplify the sentence to the following;
> 
>    Multicast routers send periodic queries within the General Query
>    timer interval (i.e., [Query Interval] value defined in [1][2]) to
>    keep the membership state up to date.

I am fine with this text. But are you sure you do not want to mention sol=
icited reports in and around this sentence. Previous sentence was trying =
to bring out that synchronization happens because general query triggers =
solicited reports.
 
> > 4. As its mentioned that 'explicit tracking function does not
> > guarantee that the membership state will always be perfectly
> > synchronized', should the task 'Per-host accounting' using this
> > function be really done? It may give incorrect results and to some
> > providers, accounting is very important. Right?
> 
> Although the explicit tracking function will contribute to accounting,
> it is not the scope of this draft. It is just a use case.
> 
> In fact, in the previous version, we said something like,
> 
>    "where this document mainly focuses on the above first and second
>    bullets in the following sections."
> 
> in the same paragraph, but removed as it's obvious. If it's better to
> mention it, I'll move it back again.
> 
> Or shall I remove the third and fourth lines? I don't mind either.

Just see below.

> > 5. Can you please elaborate on 'Maintaining multicast channel
> > characteristics'? What channel characteristics we are referring
> > here? Also how does explicit tracking function helps in this?
> 
> It is not the scope of this document, too. It is one of the use cases
> as well.
> 
> While I wrote these two lines to show the potential use cases of this
> function, if just removing these two lines is preferable, I'll remove
> it.
> 
> (But if no strong opinion, I prefer to keep these use cases as is with
> the above "where" clause. Opinion?)

I am not sure how the above two use cases uses explicit tracking function=
?

So I think it would be better to explain this in couple of sentences if y=
ou want to keep them in the draft. I understand that this may be out-of-s=
cope of this draft but as this draft is suggesting that explicit tracking=
 function is helpful in these two cases, it is better to explain how.

> > 6. In section 3.1, I did not get the need of "If there are no more
> >    receivers maintained,
> >    the router may keep the membership state information with an empty
> >    receiver list.". Does this for any specific purpose? If so, can
> >    we add this in the draft.
> 
> Allocating memory for membership state information is a cost. But I
> agree removing this sentence is reasonable as it is an implementation
> specific issue.

Ok.
 
> > 7. Should not 'Membership State Information' be deleted when the
> > corresponding multicast channel times out in the router? The router
> > should not be maintaining this multicast channel state information
> > forever. For example: if the last hosts who had joined a channel
> > goes down without sending a leave request.
> 
> It's up to the implementation as above. I'll remove such
> implementation dependent statement.

Ok.
 
> > 8. In section 3.2, in first sentence,
> >
> > In accordance with [1] and [2], whenever a router receives the State-
> > Change Report, it sends the corresponding Group-Specific or Group-
> > and-Source Specific Query messages to confirm whether or not the
> > report sender is the sole member host.
> >
> > Can we reword the above because router does not always send
> > Group-Specific or Group-and-Source Specific Query messages whenever
> > it receives a State-Change Report? We can reword it to:
> >
> > In accordance with [1] and [2], whenever a router receives the State-
> > Change Report, it might send the corresponding Group-Specific or
> Group-
> > and-Source Specific Query messages to confirm whether or not the
> > report sender was the sole member host.
> 
> No. The original sentence is correct. That behevior is defined in [1]
> and [2] as the standard behavior (without the explicit tracking
> function enabled).

What I was trying to point out is that when a router receives State-Chang=
e report, it does not always send a specific query. Please refer to the t=
able in section 6.4.2 in RFC 3376. So the above statement is not fully co=
rrect. A router sends specific query in only few cases.
 
> > Please also note the change of 'is' to 'was' in the last part of the
> sentence.
> >
> > 9. In section 3.2, in para 3, "This is in order to confirm whether
> > or not the host is the sole member."
> > -> "This is in order to confirm whether or not the host was the sole
> member."
> 
> I don't think "is" is wrong.

The host had sent a state-change report because the host does not want tr=
affic for the channel. Router sends a specific query. Router needs to con=
firm whether there is any more members for this channel. So router is con=
firming whether the host was the last member or not. That is why I sugges=
ted to use 'was'.

> > 10. In section 3.3, second para, what I infer from the first
> > sentence is that router prunes the channel after LMQI and LLQI. This
> > does not look correct. Later in the same para, last sentence correct
> > this by mentioning LMQT and LLQT is the total time router wait after
> > the first query is sent, to prune the channel. Can we fix the first
> > sentence here?
> 
> Ok, I'll remove the sentence, "before the router prunes the channel
> from the network", for LMQI/LLQI explanation.

Ok.

> > 11. A similar issue exist when LMQC and LLQC is explained in the abov=
e
> para.
> 
> I don't think so, because this sentence comes from rfc3810.

I think my comment was not clear here. What I was saying about the follow=
ing sentence was:

The [Last Member Query Count] (LMQC) and [Last
Listener Query Count] (LLQC) are the number of Group-Specific Queries
or Group-and-Source Specific Queries sent before the router assumes
there are no local members.

The last part of the sentence mention that router assumes there are no lo=
cal members after sending these many queries while router assumes there a=
re no local members only when LMQT expires. I was trying to point out thi=
s difference.
 
> > 12. Last para of section 3.3 tries to describe how a lower values of
> > LMQI/LMQC then the default suggested, can shorten the leave
> > latency. But it does not clearly articulate how explicit tracking
> > function helps if the two parameters are configured to the lower
> > values. Can we add some details on that here?
> 
> LMQI/LLQI are the standard values defined in rfc3376 and 3810. All the
> details and configurations are mentioned in them, and I believe
> repeating these descriptions in this document wouldn't be needed.

I think you did not get my question. Let me rephrase this.

Without explicit tracking function, if we lower the LMQI or LMQC or both,=
 leave latency can be reduced.

With explicit tracking function also, if we lower the LMQI or LMQC or bot=
h, leave latency can be reduced. So what is the differentiation explicit =
tracking function is bringing in here?

> > 13. In section 4, in 3rd para, in following sentence:
> >
> > The second case occurs when a router sends a specific query but does
> > not receive a State-Change Report from a downstream host within an
> > LMQT or LLQT period.
> >
> > I think when a host receives specific query, it generates a
> current-state
> > report. Right?
> 
> Right.
> As the document says "membership expectation will be inconsistent due
> to an outdated membership state", this section describes the situation
> in which report messages sent by downstream members are not reached to
> the router due to some trouble.

What I was trying to point out is that the sentence mention the 'State-ch=
ange' report while a host generates 'Current-state' report when it receiv=
es a specific query so should the sentence be using 'Current-state' repor=
t.

> > 14. As host membership protocols are unreliable, there will always
> > be a possibility of outdated membership state as packets may get
> > lost. I am not sure how does explicit tracking function lowers this
> > possibility.
> 
> This document does not say that the explicit tracking function lowers
> that possibility. This section discusses how to lower the possibility.
> If people misunderstand the point, I'll clearly say,
>     Regardless whether the explicit tracking function is enabled or
>     not, there are possibilities that a router's membership
>     expectation is inconsistent due to an outdated membership state.
> at the beginning of this section.

I think there are two issues here:

The section title is misleading. When I was reading the draft, I got an i=
mpression that explicit tracking function is lowering the possibility of =
outdated membership.

Second issue is that the section also does not clarify this clearly.

> > 15. In section 4, last para seems to explain how to fix the outdated
> > membership state that is introduced because of explicit tracking
> > function in a router while the section header seems to suggest that
> > explicit tracking function can lower the possibility of outdated
> > membership state.
> 
> No, as I said above, this document does not say that the explicit
> tracking function lowers that possibility.

Ok.

> > 16. In section 5, in first para, we established that a MLD report
> > received with unspecified source address is discarded then in second
> > para, we mention that no membership-state information is created for
> > such a request. So should we reword this to talk about only IGMP
> > case here.
> 
> I agree. I'll remove the case of using MLD's unspecified address.

Ok.
 
> > 17. In section 6, in first para, its mentioned that explicit
> > tracking does not work with older version of protocol. If I am not
> > mistaken, fast/immediate leave implemented by some vendors do
> > explicit tracking of the host. While I agree that hosts does report
> > suppression but that happens only in case its a solicited
> > report. First few (robustness count) unsolicited reports are usually
> > enough to track the host.
> 
> I don't deny a router only speaks the older version protocols can
> track the membership state only with unsolicited reports, but it has
> more risk for the router to have the outdated membership state as it
> cannot confirm the state with solicited reports.
> Moreover, switching the tracking mechanism "only with uncolicited
> reports (i.e. older version)" to "both with solicited and unsolicited
> reports (i.e. current version)" would give complexities.
> Therefore I proposed to disable the function in the older version's
> router.
> 
> BTW, this document does not prohibit to keep enabling the explicit
> tracking function in the older version's router, as it says "SHOULD
> disable", not "MUST disable". But if people prefer "MAY disable", I'd
> change "SHOULD" to "MAY" for it. Opinion?

I think a 'SHOULD' is fine here.

> > 18. In section 6, should not we talk about how the membership state
> > information is deleted when the version is lowered and the channel
> > is no more required.
> 
> Do you mean the following "MAY NOT" is not suitable for this document
> as it's implementation dependent?
> "the router MAY NOT flush the maintained membership state information"
> If so, I could agree. I'll change "MAY NOT" to "may not".

I think you did not get my question. Let me rephrase it.

This draft suggest that router create a new state to explicitly track the=
 host that are joining a channel. Let us assume that the host crashed bef=
ore sending a leave. How and when this new state maintained in the router=
 is removed?

> > 19. If we can assume that the robustness count configured in a
> > router truly represents the robustness of that network and if a
> > packet is sent this many times, the intended destination will
> > receive the packet at least once, this whole draft can be simplified
> > a lot. There is no need to generate group or group-source specific
> > queries even when all the hosts have left that channel. I am sure
> > there is something I have missed because this is how fast/immediate
> > leave is implemented for older version of protocols.
> 
> I tend to agree, but such protocol tuning is beyond the scope of this
> document.
> Also, we had discussions about specific query suppression in the
> meetings several times. Our consensus was that the specific query
> suppression should be the option (i.e. saying "SHOULD disable this
> specific query suppression" as you see in section 3.2).

I think its not protocol tuning.

A network admin should always know its robustness against unreliable prot=
ocols. So the unsolicited messages should always reach the router. If we =
say that there are chances that unsolicited reports won't reach the route=
r which are sent in multiple than in my opinion, there is no guarantee th=
at solicited messages will reach the router.

This whole concept of explicit tracking function becomes easier if we fol=
low the above logic.

Do you see an issue with the above logic?

I would also like to see what others think about this in the working grou=
p.
**************** 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 internet-drafts@ietf.org  Mon May  6 10:21:44 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA4821F88EA; Mon,  6 May 2013 10:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIHa4cBD+f+b; Mon,  6 May 2013 10:21:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0311821F853D; Mon,  6 May 2013 10:21:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p6
Message-ID: <20130506172143.12436.83074.idtracker@ietfa.amsl.com>
Date: Mon, 06 May 2013 10:21:43 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-explicit-rpf-vector-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 06 May 2013 17:21:44 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Protocol Independent Multicast Working Gr=
oup of the IETF.

	Title           : Explicit RPF Vector
	Author(s)       : Javed Asghar
                          IJsbrand Wijnands
                          Sowmya Krishnaswamy
                          Apoorva Karan
                          Vishal Arya
	Filename        : draft-ietf-pim-explicit-rpf-vector-00.txt
	Pages           : 5
	Date            : 2013-04-26

Abstract:
   This document describes a use of the Reverse Path Forwarding (RPF)
   Vector TLV as defined in [RPC 5496] to build multicast trees via an
   explicitly configured path sent in the PIM join.



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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-explicit-rpf-vector-00


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


From stig@venaas.com  Mon May  6 14:49:21 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C958821F9323 for <pim@ietfa.amsl.com>; Mon,  6 May 2013 14:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.37
X-Spam-Level: 
X-Spam-Status: No, score=-100.37 tagged_above=-999 required=5 tests=[AWL=0.369, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gnKogm127ry for <pim@ietfa.amsl.com>; Mon,  6 May 2013 14:49:21 -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 1873F21F931F for <pim@ietf.org>; Mon,  6 May 2013 14:49:20 -0700 (PDT)
Received: from [10.154.208.87] (128-107-239-235.cisco.com [128.107.239.235]) by ufisa.uninett.no (Postfix) with ESMTPSA id BD5358103; Mon,  6 May 2013 23:49:18 +0200 (CEST)
Message-ID: <5188255B.8080500@venaas.com>
Date: Mon, 06 May 2013 14:49:15 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
References: <CAL3FGfy=x=uGQ_PNkfS6ZpYyS=dAU0vaSvocou9_tDfO2iiZaQ@mail.gmail.com> <5175B9DB.3020403@venaas.com> <5175BF4D.5020109@venaas.com> <20130430.130732.146086312.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130430.130732.146086312.asaeda@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 06 May 2013 21:49:21 -0000

On 4/29/2013 9:07 PM, Hitoshi Asaeda wrote:
> Hi Stig,
>
>> The document looks good, but I see two possible issues.
>
> Thanks for your review.
>
>> Section 3.1 seems to talk too much about implementation details. In
>> particular the sentence "In order to simplify the implementation, the
>> explicit tracking function MAY NOT keep the state of (S,G) joined with
>> EXCLUDE filter mode."
>>
>> I think it's wrong here to say what the implementation MAY NOT do, in
>> particular if it is just a simplification. Advice is OK, but not
>> strict requirements for an internal implementation detail.
>
> I understand.
> I'd replace "MAY NOT" to "may not".

Are you trying to say "MAY NOT" as in strictly forbidden. Or just saying
that it does not necessarily keep the state?

>> The security considerations could be improved a bit. Potential issues
>> of
>> maintaining state are discussed, and a rate limit on membership
>> information. First of all, I don't think it is a rate limit, it's
>> should
>> be a limit on the maximum amount of memberships at any time. I think.
>
> I agree.
> I'd change the sentence in the security section as follws.
>
>     In order to prevent
>     abuse, a router enabling the explicit tracking function may need to
>     limit a total amount of membership information the router can
>     store and an amount of membership information the router can store
>     per host.

Fine.

>> Further, it should be pointed out that an attack could either cause
>> some
>> members to not be tracked, or some members to not be able to join and
>> receive.
>
> Whether report senders are malicious or not, the router can track
> their IP addresses (of course it assumes no address spoofing here,
> though).
>
> I'd say what the router should do is rate-limiting IGMP/MLD report
> transmissions per host. Do you agree on adding the following paragraph
> in the security section?
>
>     A router may rate-limit State-Change Report messages per host. When
>     the router enables rate-limiting per host, the router MAY ignore
>     the received State-Change Report messages to minimize the
>     processing overhead or prevent DoS attacks. The rate limit is left
>     to the router's implementation.
>
> BTW, while the rate limit itself is left to the router's implementation,
> is it better to specify the default timer value for the rate-limiting
> function? Or it is not necessary to specify it (as it depends on the
> implementation)?

I don't think you should specify it. That is implementation dependent.

Stig

> Regards,
> --
> Hitoshi Asaeda
>


From asaeda@sfc.wide.ad.jp  Mon May  6 19:26:33 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E6C21F939E for <pim@ietfa.amsl.com>; Mon,  6 May 2013 19:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5RiIFjQeeJo for <pim@ietfa.amsl.com>; Mon,  6 May 2013 19:26:32 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 2B55221F938E for <pim@ietf.org>; Mon,  6 May 2013 19:26:31 -0700 (PDT)
Received: from localhost (unknown [133.69.32.86]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id EB830278088; Tue,  7 May 2013 11:26:29 +0900 (JST)
Date: Tue, 07 May 2013 11:26:33 +0900 (JST)
Message-Id: <20130507.112633.137013197.asaeda@sfc.wide.ad.jp>
To: bharat_joshi@infosys.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <35347FBF2796F94E936EE76C0E6047ED32E3A122@BLRKECMBX13.ad.infosys.com>
References: <35347FBF2796F94E936EE76C0E6047ED32E39BD4@BLRKECMBX13.ad.infosys.com> <20130502.175536.137418002.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E3A122@BLRKECMBX13.ad.infosys.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 07 May 2013 02:26:33 -0000

>> > 1. In Abstract, can we remove the usage of 'fast leave' and just
>> > keep 'shortening leave latency'. A quick google search on 'fast
>> > leave' shows that it is a known term in the context of IGMPv2 where
>> > a router does not send the group specific query and stops forwarding
>> > multicast traffic for the group on that interface. As here 'fast
>> > leave' is not referring to a similar behavior, I suggest to use
>> > 'shortening leave latency' instead.
>> 
>> Fast leave itself is a general terminology. It does not specific only
>> for the IGMPv2's procedure. For example, see rfc3810 (MLDv2).
> 
> RFC 3810 defines a normal leave in IGMP term as fast leave. I am not
> sure why that term was used in MLDv2 RFC. If someone on the list
> knows, I would want to know.
> 
> As this draft talks about both IGMP/MLD, and as 'Fast leave' is
> known as two different things in IGMP and MLD, to keep abstract
> protocol independent, I would suggest to not use 'Fast leave' in
> this draft.

RFC3376 also says;
      Routers may want to track per-host membership status on an
      interface.  This allows routers to implement fast leaves (e.g.,
      for layered multicast congestion control schemes) as well as track
      membership status for possible accounting purposes.

First leave is common terminology, not dedicated for IGMPv2.
(BTW, also you can see the word, "accounting", here as the potential
use case.)

>> > 3. In third par of section 1, first sentence seems complex to me.
>> >
>> Ok, I'll simplify the sentence to the following;
>> 
>>    Multicast routers send periodic queries within the General Query
>>    timer interval (i.e., [Query Interval] value defined in [1][2]) to
>>    keep the membership state up to date.
> 
> I am fine with this text. But are you sure you do not want to
>  mention solicited reports in and around this sentence. Previous
>  sentence was trying to bring out that synchronization happens
>  because general query triggers solicited reports.

Use of solicited reports is mentioned in the second paragraph, so it's
Ok.

> So I think it would be better to explain this in couple of sentences
> if you want to keep them in the draft. I understand that this may be
> out-of-scope of this draft but as this draft is suggesting that
> explicit tracking function is helpful in these two cases, it is
> better to explain how.

Giving too much explanation for out-of-scope topics leads confusion.
As rfc3376 does, this draft should simply show the potential use
cases.
Let's keep them as is, and if I get the similar concern from others,
I'll remove these use cases.

>> > 8. In section 3.2, in first sentence,
>> >
>> > In accordance with [1] and [2], whenever a router receives the State-
>> > Change Report, it sends the corresponding Group-Specific or Group-
>> > and-Source Specific Query messages to confirm whether or not the
>> > report sender is the sole member host.
>> >
>> > Can we reword the above because router does not always send
>> > Group-Specific or Group-and-Source Specific Query messages whenever
>> > it receives a State-Change Report? We can reword it to:
>> >
>> > In accordance with [1] and [2], whenever a router receives the State-
>> > Change Report, it might send the corresponding Group-Specific or
>> Group-
>> > and-Source Specific Query messages to confirm whether or not the
>> > report sender was the sole member host.
> 
> What I was trying to point out is that when a router receives
>  State-Change report, it does not always send a specific
>  query. Please refer to the table in section 6.4.2 in RFC 3376. So
>  the above statement is not fully correct. A router sends specific
>  query in only few cases.

Ok, I understand your point.
I'll slightly change the sentence as follows;
    ... whenever a router receives the State-Change Report messages
    and changes its router state, it sends the corresponding
    Group-Specific or Group-and-Source Specific Query messages to
    confirm whether or not the report sender is the sole member host.

>> > Please also note the change of 'is' to 'was' in the last part of the
>> > sentence.
>> 
>> I don't think "is" is wrong.
> 
> The host had sent a state-change report because the host does not
> want traffic for the channel. Router sends a specific query. Router
> needs to confirm whether there is any more members for this
> channel. So router is confirming whether the host was the last
> member or not. That is why I suggested to use 'was'.

I understand your thought, but still I prefer to use "is" here,
because the router needs to confirm the current state, not the
previous state the report sender sent the report.
Let's see IESG reviewer's comment.

>> > 11. A similar issue exist when LMQC and LLQC is explained in the above
>> > para.
>> 
>> I don't think so, because this sentence comes from rfc3810.
> 
> I think my comment was not clear here. What I was saying about the
> following sentence was:
> 
> The [Last Member Query Count] (LMQC) and [Last
> Listener Query Count] (LLQC) are the number of Group-Specific Queries
> or Group-and-Source Specific Queries sent before the router assumes
> there are no local members.
> 
> The last part of the sentence mention that router assumes there are
>  no local members after sending these many queries while router
>  assumes there are no local members only when LMQT expires. I was
>  trying to point out this difference.

Your understanding is correct, and the original statement is also
correct.
The router sends specific queries these times before it assumes there
are no local members. This statement is described in both rfc3376 and
3810. Also, this statement does not inconsistent the statement, "the
router assumes there are no local members when LMQT/LLQT expires",
what you said.

>> > 12. Last para of section 3.3 tries to describe how a lower values of
>> > LMQI/LMQC then the default suggested, can shorten the leave
>> > latency. But it does not clearly articulate how explicit tracking
>> > function helps if the two parameters are configured to the lower
>> > values. Can we add some details on that here?
>> 
>> LMQI/LLQI are the standard values defined in rfc3376 and 3810. All the
>> details and configurations are mentioned in them, and I believe
>> repeating these descriptions in this document wouldn't be needed.
> 
> I think you did not get my question. Let me rephrase this.
> 
> Without explicit tracking function, if we lower the LMQI or LMQC or
> both, leave latency can be reduced.
> 
> With explicit tracking function also, if we lower the LMQI or LMQC
> or both, leave latency can be reduced. So what is the
> differentiation explicit tracking function is bringing in here?

Comparing with no tracking condition, the explicit tracking function
lowers the risk of wrong membership expectation. Therefore with the
explicit tracking function, LMQI/LLQI can be shorter and LMQC/LLQC can
be smaller than both default values.
This is the reason that this doc says;
   the LMQI/LLQI MAY be set to 1 second or shorter. The LMQC/LLQC
   values MAY be set to 1 for the router, whereas their default values
   are the [Robustness Variable] value whose default value is 2.

>> > 13. In section 4, in 3rd para, in following sentence:
>> >
>> > The second case occurs when a router sends a specific query but does
>> > not receive a State-Change Report from a downstream host within an
>> > LMQT or LLQT period.
>> >
>> > I think when a host receives specific query, it generates a
>> current-state
>> > report. Right?
>> 
>> Right.
>> As the document says "membership expectation will be inconsistent due
>> to an outdated membership state", this section describes the situation
>> in which report messages sent by downstream members are not reached to
>> the router due to some trouble.
> 
> What I was trying to point out is that the sentence mention the
> 'State-change' report while a host generates 'Current-state' report
> when it receives a specific query so should the sentence be using
> 'Current-state' report.

Oh, good catch. It's typo. Thanks.

>> > 14. As host membership protocols are unreliable, there will always
>> > be a possibility of outdated membership state as packets may get
>> > lost. I am not sure how does explicit tracking function lowers this
>> > possibility.
>> 
>> This document does not say that the explicit tracking function lowers
>> that possibility. This section discusses how to lower the possibility.
>> If people misunderstand the point, I'll clearly say,
>>     Regardless whether the explicit tracking function is enabled or
>>     not, there are possibilities that a router's membership
>>     expectation is inconsistent due to an outdated membership state.
>> at the beginning of this section.
> 
> I think there are two issues here:
> 
> The section title is misleading. When I was reading the draft, I got
> an impression that explicit tracking function is lowering the
> possibility of outdated membership.

Ok, then how about, "Lowering the Risk of Wrong Membership
Expectation"?

> Second issue is that the section also does not clarify this clearly.

So as I said how about adding the followin sentence at the beginning
of this section?

   Regardless whether the explicit tracking function is enabled or
   not, there are possibilities that a router's membership
   expectation is inconsistent due to an outdated membership state.

>> > 18. In section 6, should not we talk about how the membership state
>> > information is deleted when the version is lowered and the channel
>> > is no more required.
>> 
>> Do you mean the following "MAY NOT" is not suitable for this document
>> as it's implementation dependent?
>> "the router MAY NOT flush the maintained membership state information"
>> If so, I could agree. I'll change "MAY NOT" to "may not".
> 
> I think you did not get my question. Let me rephrase it.
> 
> This draft suggest that router create a new state to explicitly
> track the host that are joining a channel. Let us assume that the
> host crashed before sending a leave. How and when this new state
> maintained in the router is removed?

Maybe I don't still understand your question.
If you are talking about outdated membership status due to the
maintained host crash, the membership status will be updated by
general query as mentioned in section 4.
If you are talking about the statement of flushing the maintained
membership state information in the older version compatibility mode,
if you think this behavior is implementation dependend, I'm Ok to
remove the statements starting from "On the other hand" in section 6.
Or other way you prefer?

>> > 19. If we can assume that the robustness count configured in a
>> > router truly represents the robustness of that network and if a
>> > packet is sent this many times, the intended destination will
>> > receive the packet at least once, this whole draft can be simplified
>> > a lot. There is no need to generate group or group-source specific
>> > queries even when all the hosts have left that channel. I am sure
>> > there is something I have missed because this is how fast/immediate
>> > leave is implemented for older version of protocols.
>> 
>> I tend to agree, but such protocol tuning is beyond the scope of this
>> document.
>> Also, we had discussions about specific query suppression in the
>> meetings several times. Our consensus was that the specific query
>> suppression should be the option (i.e. saying "SHOULD disable this
>> specific query suppression" as you see in section 3.2).
> 
> I think its not protocol tuning.
> 
> A network admin should always know its robustness against unreliable
> protocols. So the unsolicited messages should always reach the
> router. If we say that there are chances that unsolicited reports
> won't reach the router which are sent in multiple than in my
> opinion, there is no guarantee that solicited messages will reach
> the router.
> 
> This whole concept of explicit tracking function becomes easier if
> we follow the above logic.
> 
> Do you see an issue with the above logic?

I agree such discussion is interesting, but it is beyond the scope of
this document.
The solution regarding how the protocol robustness is improved and how
the message transmission is guaranteed is not simple. It is not solved
only with the explicit tracking function.
I'm happy to work on this topic, but it is not a good idea to discuss
such solution in this document.
(Note that the IGMP/MLD protocol tuning mainly for wireless and mobile
environment is issued in rfc6636 and the more general protocol
modification discussion is on going in the Mike's I-D.)

Regards,
--
Hitoshi Asaeda

From asaeda@sfc.wide.ad.jp  Mon May  6 19:32:57 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F33921F92E1 for <pim@ietfa.amsl.com>; Mon,  6 May 2013 19:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.299
X-Spam-Level: 
X-Spam-Status: No, score=-101.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIhu32Gmly8X for <pim@ietfa.amsl.com>; Mon,  6 May 2013 19:32:56 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 961EB21F92CB for <pim@ietf.org>; Mon,  6 May 2013 19:32:56 -0700 (PDT)
Received: from localhost (unknown [133.69.32.86]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id AAE29278088; Tue,  7 May 2013 11:32:55 +0900 (JST)
Date: Tue, 07 May 2013 11:33:09 +0900 (JST)
Message-Id: <20130507.113309.128188124.asaeda@sfc.wide.ad.jp>
To: stig@venaas.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <5188255B.8080500@venaas.com>
References: <5175BF4D.5020109@venaas.com> <20130430.130732.146086312.asaeda@sfc.wide.ad.jp> <5188255B.8080500@venaas.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 07 May 2013 02:32:57 -0000

>>> Section 3.1 seems to talk too much about implementation details. In
>>> particular the sentence "In order to simplify the implementation, the
>>> explicit tracking function MAY NOT keep the state of (S,G) joined with
>>> EXCLUDE filter mode."
>>>
>>> I think it's wrong here to say what the implementation MAY NOT do, in
>>> particular if it is just a simplification. Advice is OK, but not
>>> strict requirements for an internal implementation detail.
>>
>> I understand.
>> I'd replace "MAY NOT" to "may not".
> 
> Are you trying to say "MAY NOT" as in strictly forbidden. Or just
> saying
> that it does not necessarily keep the state?

While I agree detailing the implementation specs is not needed in this
doc, I believe "the explicit tracking function may not keep the state
of (S,G) joined with EXCLUDE filter mode" is an important advice or
guideline for its implementation. So, I keep this statement without
RFC2119's words.

>>> Further, it should be pointed out that an attack could either cause
>>> some
>>> members to not be tracked, or some members to not be able to join and
>>> receive.
>>
>> Whether report senders are malicious or not, the router can track
>> their IP addresses (of course it assumes no address spoofing here,
>> though).
>>
>> I'd say what the router should do is rate-limiting IGMP/MLD report
>> transmissions per host. Do you agree on adding the following paragraph
>> in the security section?
>>
>>     A router may rate-limit State-Change Report messages per host. When
>>     the router enables rate-limiting per host, the router MAY ignore
>>     the received State-Change Report messages to minimize the
>>     processing overhead or prevent DoS attacks. The rate limit is left
>>     to the router's implementation.
>>
>> BTW, while the rate limit itself is left to the router's
>> implementation,
>> is it better to specify the default timer value for the rate-limiting
>> function? Or it is not necessary to specify it (as it depends on the
>> implementation)?
> 
> I don't think you should specify it. That is implementation dependent.

Got it.
Thanks.

Regards,
--
Hitoshi Asaeda

From bharat_joshi@infosys.com  Tue May  7 00:45:16 2013
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDED721F8FDF for <pim@ietfa.amsl.com>; Tue,  7 May 2013 00:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4Lhs-dqa3HO for <pim@ietfa.amsl.com>; Tue,  7 May 2013 00:45:11 -0700 (PDT)
Received: from kecgate06.infosys.com (kecgate06.infosys.com [122.98.14.33]) by ietfa.amsl.com (Postfix) with ESMTP id 17D1421F9017 for <pim@ietf.org>; Tue,  7 May 2013 00:45:07 -0700 (PDT)
X-TM-IMSS-Message-ID: <6127786f000007f1@infosys.com>
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by infosys.com ([122.98.14.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 6127786f000007f1 ; Tue, 7 May 2013 13:19:32 +0530
Received: from BLRKECHUB08.ad.infosys.com (10.66.236.138) by blrkechub04.ad.infosys.com (10.66.236.44) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 7 May 2013 13:14:38 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by BLRKECHUB08.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Tue, 7 May 2013 13:14:38 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
Thread-Topic: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
Thread-Index: AQHOQduqGQSf6F+FGk6WsRG8zxIhsJjufku8gALHaQCAAHXTcoAG+SKAgACio7c=
Date: Tue, 7 May 2013 07:44:37 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com>
References: <35347FBF2796F94E936EE76C0E6047ED32E39BD4@BLRKECMBX13.ad.infosys.com> <20130502.175536.137418002.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E3A122@BLRKECMBX13.ad.infosys.com>, <20130507.112633.137013197.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130507.112633.137013197.asaeda@sfc.wide.ad.jp>
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
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 07 May 2013 07:45:17 -0000

Hi Hitoshi,

     Please see my responses in line.

Regards,
Bharat

>> > 1. In Abstract, can we remove the usage of 'fast leave' and just
> >> > keep 'shortening leave latency'. A quick google search on 'fast
> >> > leave' shows that it is a known term in the context of IGMPv2 wher=
e
> >> > a router does not send the group specific query and stops
> forwarding
> >> > multicast traffic for the group on that interface. As here 'fast
> >> > leave' is not referring to a similar behavior, I suggest to use
> >> > 'shortening leave latency' instead.
> >> 
> >> Fast leave itself is a general terminology. It does not specific onl=
y
> >> for the IGMPv2's procedure. For example, see rfc3810 (MLDv2).
> > 
> > RFC 3810 defines a normal leave in IGMP term as fast leave. I am not
> > sure why that term was used in MLDv2 RFC. If someone on the list
> > knows, I would want to know.
> > 
> > As this draft talks about both IGMP/MLD, and as 'Fast leave' is
> > known as two different things in IGMP and MLD, to keep abstract
> > protocol independent, I would suggest to not use 'Fast leave' in
> > this draft.
> 
> RFC3376 also says;
>       Routers may want to track per-host membership status on an
>       interface.  This allows routers to implement fast leaves (e.g.,
>       for layered multicast congestion control schemes) as well as trac=
k
>       membership status for possible accounting purposes.
> 
> First leave is common terminology, not dedicated for IGMPv2.
> (BTW, also you can see the word, "accounting", here as the potential
> use case.)

Ok.
 
> >> > 3. In third par of section 1, first sentence seems complex to me.
> >> >
> >> Ok, I'll simplify the sentence to the following;
> >> 
> >>    Multicast routers send periodic queries within the General Query
> >>    timer interval (i.e., [Query Interval] value defined in [1][2]) t=
o
> >>    keep the membership state up to date.
> > 
> > I am fine with this text. But are you sure you do not want to
> >  mention solicited reports in and around this sentence. Previous
> >  sentence was trying to bring out that synchronization happens
> >  because general query triggers solicited reports.
> 
> Use of solicited reports is mentioned in the second paragraph, so it's
> Ok.

Ok.

> > So I think it would be better to explain this in couple of sentences
> > if you want to keep them in the draft. I understand that this may be
> > out-of-scope of this draft but as this draft is suggesting that
> > explicit tracking function is helpful in these two cases, it is
> > better to explain how.
> 
> Giving too much explanation for out-of-scope topics leads confusion.
> As rfc3376 does, this draft should simply show the potential use
> cases.
> Let's keep them as is, and if I get the similar concern from others,
> I'll remove these use cases.
>

I was not suggesting to add too much explanation. But it will be better i=
f you can add some details or refer to another document/draft.

> >> > 8. In section 3.2, in first sentence,
> >> >
> >> > In accordance with [1] and [2], whenever a router receives the
> State-
> >> > Change Report, it sends the corresponding Group-Specific or Group-
> >> > and-Source Specific Query messages to confirm whether or not the
> >> > report sender is the sole member host.
> >> >
> >> > Can we reword the above because router does not always send
> >> > Group-Specific or Group-and-Source Specific Query messages wheneve=
r
> >> > it receives a State-Change Report? We can reword it to:
> >> >
> >> > In accordance with [1] and [2], whenever a router receives the
> State-
> >> > Change Report, it might send the corresponding Group-Specific or
> >> Group-
> >> > and-Source Specific Query messages to confirm whether or not the
> >> > report sender was the sole member host.
> > 
> > What I was trying to point out is that when a router receives
> >  State-Change report, it does not always send a specific
> >  query. Please refer to the table in section 6.4.2 in RFC 3376. So
> >  the above statement is not fully correct. A router sends specific
> >  query in only few cases.
> 
> Ok, I understand your point.
> I'll slightly change the sentence as follows;
>     ... whenever a router receives the State-Change Report messages
>     and changes its router state, it sends the corresponding
>     Group-Specific or Group-and-Source Specific Query messages to
>     confirm whether or not the report sender is the sole member host.

The point I was trying to put across is that "router might send" as it de=
pends upon the state of that channel so the updated sentence still says '=
it sends the corresponding' which I feel is not correct.
 
> >> > Please also note the change of 'is' to 'was' in the last part of
> the
> >> > sentence.
> >> 
> >> I don't think "is" is wrong.
> > 
> > The host had sent a state-change report because the host does not
> > want traffic for the channel. Router sends a specific query. Router
> > needs to confirm whether there is any more members for this
> > channel. So router is confirming whether the host was the last
> > member or not. That is why I suggested to use 'was'.
> 
> I understand your thought, but still I prefer to use "is" here,
> because the router needs to confirm the current state, not the
> previous state the report sender sent the report.
> Let's see IESG reviewer's comment.

Ok. I will leave this to the working group and IESG.

> >> > 11. A similar issue exist when LMQC and LLQC is explained in the
> above
> >> > para.
> >> 
> >> I don't think so, because this sentence comes from rfc3810.
> > 
> > I think my comment was not clear here. What I was saying about the
> > following sentence was:
> > 
> > The [Last Member Query Count] (LMQC) and [Last
> > Listener Query Count] (LLQC) are the number of Group-Specific Queries
> > or Group-and-Source Specific Queries sent before the router assumes
> > there are no local members.
> > 
> > The last part of the sentence mention that router assumes there are
> >  no local members after sending these many queries while router
> >  assumes there are no local members only when LMQT expires. I was
> >  trying to point out this difference.
> 
> Your understanding is correct, and the original statement is also
> correct.
> The router sends specific queries these times before it assumes there
> are no local members. This statement is described in both rfc3376 and
> 3810. Also, this statement does not inconsistent the statement, "the
> router assumes there are no local members when LMQT/LLQT expires",
> what you said.

Ok. I was just trying to avoid little confusion with the above sentence.

> >> > 12. Last para of section 3.3 tries to describe how a lower values
> of
> >> > LMQI/LMQC then the default suggested, can shorten the leave
> >> > latency. But it does not clearly articulate how explicit tracking
> >> > function helps if the two parameters are configured to the lower
> >> > values. Can we add some details on that here?
> >> 
> >> LMQI/LLQI are the standard values defined in rfc3376 and 3810. All
> the
> >> details and configurations are mentioned in them, and I believe
> >> repeating these descriptions in this document wouldn't be needed.
> > 
> > I think you did not get my question. Let me rephrase this.
> > 
> > Without explicit tracking function, if we lower the LMQI or LMQC or
> > both, leave latency can be reduced.
> > 
> > With explicit tracking function also, if we lower the LMQI or LMQC
> > or both, leave latency can be reduced. So what is the
> > differentiation explicit tracking function is bringing in here?
> 
> Comparing with no tracking condition, the explicit tracking function
> lowers the risk of wrong membership expectation. Therefore with the
> explicit tracking function, LMQI/LLQI can be shorter and LMQC/LLQC can
> be smaller than both default values.
> This is the reason that this doc says;
>    the LMQI/LLQI MAY be set to 1 second or shorter. The LMQC/LLQC
>    values MAY be set to 1 for the router, whereas their default values
>    are the [Robustness Variable] value whose default value is 2.

I am not sure if I follow you. Explicit tracking function might be loweri=
ng the risk of wrong membership expectation but is not eliminating it. 

So from a real would perspective, why would an administrator would lik to=
 reduce leave latency if he is not sure about something.

> >> > 13. In section 4, in 3rd para, in following sentence:
> >> >
> >> > The second case occurs when a router sends a specific query but
> does
> >> > not receive a State-Change Report from a downstream host within an
> >> > LMQT or LLQT period.
> >> >
> >> > I think when a host receives specific query, it generates a
> >> current-state
> >> > report. Right?
> >> 
> >> Right.
> >> As the document says "membership expectation will be inconsistent du=
e
> >> to an outdated membership state", this section describes the
> situation
> >> in which report messages sent by downstream members are not reached
> to
> >> the router due to some trouble.
> > 
> > What I was trying to point out is that the sentence mention the
> > 'State-change' report while a host generates 'Current-state' report
> > when it receives a specific query so should the sentence be using
> > 'Current-state' report.
> 
> Oh, good catch. It's typo. Thanks.

Ok.

> >> > 14. As host membership protocols are unreliable, there will always
> >> > be a possibility of outdated membership state as packets may get
> >> > lost. I am not sure how does explicit tracking function lowers thi=
s
> >> > possibility.
> >> 
> >> This document does not say that the explicit tracking function lower=
s
> >> that possibility. This section discusses how to lower the
> possibility.
> >> If people misunderstand the point, I'll clearly say,
> >>     Regardless whether the explicit tracking function is enabled or
> >>     not, there are possibilities that a router's membership
> >>     expectation is inconsistent due to an outdated membership state.
> >> at the beginning of this section.
> > 
> > I think there are two issues here:
> > 
> > The section title is misleading. When I was reading the draft, I got
> > an impression that explicit tracking function is lowering the
> > possibility of outdated membership.
> 
> Ok, then how about, "Lowering the Risk of Wrong Membership
> Expectation"?

It still does not indicate that we are talking about this when explicit t=
racking function is enabled. I would like to see something like:

Lowering the Risk of Wrong Membership Expectation with Explicit Tracking =
function enabled

> > Second issue is that the section also does not clarify this clearly.
> 
> So as I said how about adding the followin sentence at the beginning
> of this section?
> 
>    Regardless whether the explicit tracking function is enabled or
>    not, there are possibilities that a router's membership
>    expectation is inconsistent due to an outdated membership state.

Ok. With the above suggested type of title and your suggested text, thing=
s will be far more clearer.

> >> > 18. In section 6, should not we talk about how the membership stat=
e
> >> > information is deleted when the version is lowered and the channel
> >> > is no more required.
> >> 
> >> Do you mean the following "MAY NOT" is not suitable for this documen=
t
> >> as it's implementation dependent?
> >> "the router MAY NOT flush the maintained membership state
> information"
> >> If so, I could agree. I'll change "MAY NOT" to "may not".
> > 
> > I think you did not get my question. Let me rephrase it.
> > 
> > This draft suggest that router create a new state to explicitly
> > track the host that are joining a channel. Let us assume that the
> > host crashed before sending a leave. How and when this new state
> > maintained in the router is removed?
> 
> Maybe I don't still understand your question.
> If you are talking about outdated membership status due to the
> maintained host crash, the membership status will be updated by
> general query as mentioned in section 4.
> If you are talking about the statement of flushing the maintained
> membership state information in the older version compatibility mode,
> if you think this behavior is implementation dependend, I'm Ok to
> remove the statements starting from "On the other hand" in section 6.
> Or other way you prefer?

I was talking about the first case. I am into implementation. Let me tell=
 you what I think:

1. The router create this new membership state and keep it updated when i=
t receives reports. The router probably aggregate these reports to create=
 forwarding state.
2. This new membership state gets removed if the last host sends a state-=
change report to leave this channel.

What I am asking is that when is this new membership state removed if the=
 last host has crashed and did not send this state-change report. 

Will not we need to link this membership state to the forwarding state ro=
uter maintains. This way when the group or source timer fires apart from =
the forwarding state this membership state is also removed. Does this mak=
e sense?

The reason for asking this question is that no timer is maintained for th=
is new membership state so there is no way to time out only memership sta=
te.

> >> > 19. If we can assume that the robustness count configured in a
> >> > router truly represents the robustness of that network and if a
> >> > packet is sent this many times, the intended destination will
> >> > receive the packet at least once, this whole draft can be
> simplified
> >> > a lot. There is no need to generate group or group-source specific
> >> > queries even when all the hosts have left that channel. I am sure
> >> > there is something I have missed because this is how fast/immediat=
e
> >> > leave is implemented for older version of protocols.
> >> 
> >> I tend to agree, but such protocol tuning is beyond the scope of thi=
s
> >> document.
> >> Also, we had discussions about specific query suppression in the
> >> meetings several times. Our consensus was that the specific query
> >> suppression should be the option (i.e. saying "SHOULD disable this
> >> specific query suppression" as you see in section 3.2).
> > 
> > I think its not protocol tuning.
> > 
> > A network admin should always know its robustness against unreliable
> > protocols. So the unsolicited messages should always reach the
> > router. If we say that there are chances that unsolicited reports
> > won't reach the router which are sent in multiple than in my
> > opinion, there is no guarantee that solicited messages will reach
> > the router.
> > 
> > This whole concept of explicit tracking function becomes easier if
> > we follow the above logic.
> > 
> > Do you see an issue with the above logic?
> 
> I agree such discussion is interesting, but it is beyond the scope of
> this document.

I am not sure I understand.

> The solution regarding how the protocol robustness is improved and how
> the message transmission is guaranteed is not simple. It is not solved
> only with the explicit tracking function.

I was not talking about how to improve the protocol robustness here.

What I am suggesting is that, with robustness count, things have been wor=
king in the field for so many years. So why not make the whole explicit t=
racking functionality easier by assuming that unsolicited reports are not=
 lost, than what is proposed in this draft?

> I'm happy to work on this topic, but it is not a good idea to discuss
> such solution in this document.
> (Note that the IGMP/MLD protocol tuning mainly for wireless and mobile
> environment is issued in rfc6636 and the more general protocol
> modification discussion is on going in the Mike's I-D.)
**************** 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 stig@venaas.com  Tue May  7 09:28:00 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B6D21F9254 for <pim@ietfa.amsl.com>; Tue,  7 May 2013 09:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tV3UpjJ9-jqz for <pim@ietfa.amsl.com>; Tue,  7 May 2013 09:27:59 -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 D4F6F21F8F3C for <pim@ietf.org>; Tue,  7 May 2013 09:27:58 -0700 (PDT)
Received: from [IPv6:2001:420:4:ea0c:f9c1:dccb:fdeb:7088] (unknown [IPv6:2001:420:4:ea0c:f9c1:dccb:fdeb:7088]) by ufisa.uninett.no (Postfix) with ESMTPSA id CC77B812F; Tue,  7 May 2013 18:27:56 +0200 (CEST)
Message-ID: <51892B8B.70705@venaas.com>
Date: Tue, 07 May 2013 09:27:55 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: pim@ietf.org
References: <CAL3FGfy=x=uGQ_PNkfS6ZpYyS=dAU0vaSvocou9_tDfO2iiZaQ@mail.gmail.com> <5175B9DB.3020403@venaas.com>
In-Reply-To: <5175B9DB.3020403@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mike McBride <mmcbride7@gmail.com>
Subject: Re: [pim] draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 07 May 2013 16:28:00 -0000

We believe we have sufficient support for this document to move it
forward to the IESG. We will however need a new document that addresses
comments made during the WGLC. Once we have a new version addressing the
comments we'll give the WG a few days to comment on the new version, and
unless issues are raised, send it off to the IESG.

Stig

From stig@venaas.com  Wed May  8 09:57:19 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59B2821F8C23 for <pim@ietfa.amsl.com>; Wed,  8 May 2013 09:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.856
X-Spam-Level: 
X-Spam-Status: No, score=-101.856 tagged_above=-999 required=5 tests=[AWL=0.743, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pnbhcJ56O6+l for <pim@ietfa.amsl.com>; Wed,  8 May 2013 09:57:19 -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 C1CE121F8A48 for <pim@ietf.org>; Wed,  8 May 2013 09:57:18 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 5825C8123; Wed,  8 May 2013 18:57:17 +0200 (CEST)
Message-ID: <518A83EA.1060408@venaas.com>
Date: Wed, 08 May 2013 09:57:14 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
References: <5175BF4D.5020109@venaas.com> <20130430.130732.146086312.asaeda@sfc.wide.ad.jp> <5188255B.8080500@venaas.com> <20130507.113309.128188124.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130507.113309.128188124.asaeda@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 08 May 2013 16:57:19 -0000

Hi Hitoshi

On 5/6/2013 7:33 PM, Hitoshi Asaeda wrote:
>>>> Section 3.1 seems to talk too much about implementation details. In
>>>> particular the sentence "In order to simplify the implementation, the
>>>> explicit tracking function MAY NOT keep the state of (S,G) joined with
>>>> EXCLUDE filter mode."
>>>>
>>>> I think it's wrong here to say what the implementation MAY NOT do, in
>>>> particular if it is just a simplification. Advice is OK, but not
>>>> strict requirements for an internal implementation detail.
>>>
>>> I understand.
>>> I'd replace "MAY NOT" to "may not".
>>
>> Are you trying to say "MAY NOT" as in strictly forbidden. Or just
>> saying
>> that it does not necessarily keep the state?

MAY NOT is not defined in RFC 2119, so I think you need to change the
other occurrences as well. Also it is not clear what the meaning is I
think. MAY NOT could be read as MUST NOT. I suspect that the places
where it says "MAY NOT" can be "may not", but it depends on what you're
trying to say.

Stig


From stig@venaas.com  Wed May  8 13:46:48 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A756621F8E49 for <pim@ietfa.amsl.com>; Wed,  8 May 2013 13:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.153
X-Spam-Level: 
X-Spam-Status: No, score=-102.153 tagged_above=-999 required=5 tests=[AWL=0.446, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mRftdcnpqW2q for <pim@ietfa.amsl.com>; Wed,  8 May 2013 13:46:47 -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 722F721F8EBD for <pim@ietf.org>; Wed,  8 May 2013 13:46:46 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 6A9408130; Wed,  8 May 2013 22:46:44 +0200 (CEST)
Message-ID: <518AB9B1.7010601@venaas.com>
Date: Wed, 08 May 2013 13:46:41 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Bharat Joshi <bharat_joshi@infosys.com>
References: <35347FBF2796F94E936EE76C0E6047ED32E39BD4@BLRKECMBX13.ad.infosys.com> <20130502.175536.137418002.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E3A122@BLRKECMBX13.ad.infosys.com>, <20130507.112633.137013197.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com>
In-Reply-To: <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 08 May 2013 20:46:48 -0000

Hi

Some comments on this (as an individual contributor).

On 5/7/2013 12:44 AM, Bharat Joshi wrote:
> Hi Hitoshi,
>
>       Please see my responses in line.
>
> Regards,
> Bharat
>
>>>> 1. In Abstract, can we remove the usage of 'fast leave' and just
>>>>> keep 'shortening leave latency'. A quick google search on 'fast
>>>>> leave' shows that it is a known term in the context of IGMPv2 where
>>>>> a router does not send the group specific query and stops
>> forwarding
>>>>> multicast traffic for the group on that interface. As here 'fast
>>>>> leave' is not referring to a similar behavior, I suggest to use
>>>>> 'shortening leave latency' instead.
>>>>
>>>> Fast leave itself is a general terminology. It does not specific only
>>>> for the IGMPv2's procedure. For example, see rfc3810 (MLDv2).
>>>
>>> RFC 3810 defines a normal leave in IGMP term as fast leave. I am not
>>> sure why that term was used in MLDv2 RFC. If someone on the list
>>> knows, I would want to know.
>>>
>>> As this draft talks about both IGMP/MLD, and as 'Fast leave' is
>>> known as two different things in IGMP and MLD, to keep abstract
>>> protocol independent, I would suggest to not use 'Fast leave' in
>>> this draft.
>>
>> RFC3376 also says;
>>        Routers may want to track per-host membership status on an
>>        interface.  This allows routers to implement fast leaves (e.g.,
>>        for layered multicast congestion control schemes) as well as track
>>        membership status for possible accounting purposes.
>>
>> First leave is common terminology, not dedicated for IGMPv2.
>> (BTW, also you can see the word, "accounting", here as the potential
>> use case.)
>
> Ok.

Even though I'm fine with the term "fast leave", I think the abstract
reads better if it just says:

    This document describes the IGMP/MLD-based explicit membership
    tracking function for multicast routers supporting IGMPv3/MLDv2.  The
    explicit tracking function contributes to saving network resources
    and shortening leave latency.

There is no need to introduce any terms in the abstract, the main thing
is that the leave latency is shorter.

>>>>> 3. In third par of section 1, first sentence seems complex to me.
>>>>>
>>>> Ok, I'll simplify the sentence to the following;
>>>>
>>>>     Multicast routers send periodic queries within the General Query
>>>>     timer interval (i.e., [Query Interval] value defined in [1][2]) to
>>>>     keep the membership state up to date.
>>>
>>> I am fine with this text. But are you sure you do not want to
>>>   mention solicited reports in and around this sentence. Previous
>>>   sentence was trying to bring out that synchronization happens
>>>   because general query triggers solicited reports.
>>
>> Use of solicited reports is mentioned in the second paragraph, so it's
>> Ok.
>
> Ok.
>
>>> So I think it would be better to explain this in couple of sentences
>>> if you want to keep them in the draft. I understand that this may be
>>> out-of-scope of this draft but as this draft is suggesting that
>>> explicit tracking function is helpful in these two cases, it is
>>> better to explain how.
>>
>> Giving too much explanation for out-of-scope topics leads confusion.
>> As rfc3376 does, this draft should simply show the potential use
>> cases.
>> Let's keep them as is, and if I get the similar concern from others,
>> I'll remove these use cases.
>>
>
> I was not suggesting to add too much explanation. But it will be better if you can add some details or refer to another document/draft.
>
>>>>> 8. In section 3.2, in first sentence,
>>>>>
>>>>> In accordance with [1] and [2], whenever a router receives the
>> State-
>>>>> Change Report, it sends the corresponding Group-Specific or Group-
>>>>> and-Source Specific Query messages to confirm whether or not the
>>>>> report sender is the sole member host.
>>>>>
>>>>> Can we reword the above because router does not always send
>>>>> Group-Specific or Group-and-Source Specific Query messages whenever
>>>>> it receives a State-Change Report? We can reword it to:
>>>>>
>>>>> In accordance with [1] and [2], whenever a router receives the
>> State-
>>>>> Change Report, it might send the corresponding Group-Specific or
>>>> Group-
>>>>> and-Source Specific Query messages to confirm whether or not the
>>>>> report sender was the sole member host.
>>>
>>> What I was trying to point out is that when a router receives
>>>   State-Change report, it does not always send a specific
>>>   query. Please refer to the table in section 6.4.2 in RFC 3376. So
>>>   the above statement is not fully correct. A router sends specific
>>>   query in only few cases.
>>
>> Ok, I understand your point.
>> I'll slightly change the sentence as follows;
>>      ... whenever a router receives the State-Change Report messages
>>      and changes its router state, it sends the corresponding
>>      Group-Specific or Group-and-Source Specific Query messages to
>>      confirm whether or not the report sender is the sole member host.
>
> The point I was trying to put across is that "router might send" as it depends upon the state of that channel so the updated sentence still says 'it sends the corresponding' which I feel is not correct.

I agree this text needs to change. It says "whenever a router receives
the State-Change Report messages and changes its router state", which
means that for any such change a specific query is sent. But there are
state changes where you do not send a specific query. E.g. if a host
adds a new source (top row in the table in RFC 3376 section 6.4.2), a
specific query is not sent.

>>>>> Please also note the change of 'is' to 'was' in the last part of
>> the
>>>>> sentence.
>>>>
>>>> I don't think "is" is wrong.
>>>
>>> The host had sent a state-change report because the host does not
>>> want traffic for the channel. Router sends a specific query. Router
>>> needs to confirm whether there is any more members for this
>>> channel. So router is confirming whether the host was the last
>>> member or not. That is why I suggested to use 'was'.
>>
>> I understand your thought, but still I prefer to use "is" here,
>> because the router needs to confirm the current state, not the
>> previous state the report sender sent the report.
>> Let's see IESG reviewer's comment.
>
> Ok. I will leave this to the working group and IESG.
>
>>>>> 11. A similar issue exist when LMQC and LLQC is explained in the
>> above
>>>>> para.
>>>>
>>>> I don't think so, because this sentence comes from rfc3810.
>>>
>>> I think my comment was not clear here. What I was saying about the
>>> following sentence was:
>>>
>>> The [Last Member Query Count] (LMQC) and [Last
>>> Listener Query Count] (LLQC) are the number of Group-Specific Queries
>>> or Group-and-Source Specific Queries sent before the router assumes
>>> there are no local members.
>>>
>>> The last part of the sentence mention that router assumes there are
>>>   no local members after sending these many queries while router
>>>   assumes there are no local members only when LMQT expires. I was
>>>   trying to point out this difference.
>>
>> Your understanding is correct, and the original statement is also
>> correct.
>> The router sends specific queries these times before it assumes there
>> are no local members. This statement is described in both rfc3376 and
>> 3810. Also, this statement does not inconsistent the statement, "the
>> router assumes there are no local members when LMQT/LLQT expires",
>> what you said.
>
> Ok. I was just trying to avoid little confusion with the above sentence.
>
>>>>> 12. Last para of section 3.3 tries to describe how a lower values
>> of
>>>>> LMQI/LMQC then the default suggested, can shorten the leave
>>>>> latency. But it does not clearly articulate how explicit tracking
>>>>> function helps if the two parameters are configured to the lower
>>>>> values. Can we add some details on that here?
>>>>
>>>> LMQI/LLQI are the standard values defined in rfc3376 and 3810. All
>> the
>>>> details and configurations are mentioned in them, and I believe
>>>> repeating these descriptions in this document wouldn't be needed.
>>>
>>> I think you did not get my question. Let me rephrase this.
>>>
>>> Without explicit tracking function, if we lower the LMQI or LMQC or
>>> both, leave latency can be reduced.
>>>
>>> With explicit tracking function also, if we lower the LMQI or LMQC
>>> or both, leave latency can be reduced. So what is the
>>> differentiation explicit tracking function is bringing in here?
>>
>> Comparing with no tracking condition, the explicit tracking function
>> lowers the risk of wrong membership expectation. Therefore with the
>> explicit tracking function, LMQI/LLQI can be shorter and LMQC/LLQC can
>> be smaller than both default values.
>> This is the reason that this doc says;
>>     the LMQI/LLQI MAY be set to 1 second or shorter. The LMQC/LLQC
>>     values MAY be set to 1 for the router, whereas their default values
>>     are the [Robustness Variable] value whose default value is 2.
>
> I am not sure if I follow you. Explicit tracking function might be lowering the risk of wrong membership expectation but is not eliminating it.
>
> So from a real would perspective, why would an administrator would lik to reduce leave latency if he is not sure about something.
>
>>>>> 13. In section 4, in 3rd para, in following sentence:
>>>>>
>>>>> The second case occurs when a router sends a specific query but
>> does
>>>>> not receive a State-Change Report from a downstream host within an
>>>>> LMQT or LLQT period.
>>>>>
>>>>> I think when a host receives specific query, it generates a
>>>> current-state
>>>>> report. Right?
>>>>
>>>> Right.
>>>> As the document says "membership expectation will be inconsistent due
>>>> to an outdated membership state", this section describes the
>> situation
>>>> in which report messages sent by downstream members are not reached
>> to
>>>> the router due to some trouble.
>>>
>>> What I was trying to point out is that the sentence mention the
>>> 'State-change' report while a host generates 'Current-state' report
>>> when it receives a specific query so should the sentence be using
>>> 'Current-state' report.
>>
>> Oh, good catch. It's typo. Thanks.
>
> Ok.
>
>>>>> 14. As host membership protocols are unreliable, there will always
>>>>> be a possibility of outdated membership state as packets may get
>>>>> lost. I am not sure how does explicit tracking function lowers this
>>>>> possibility.
>>>>
>>>> This document does not say that the explicit tracking function lowers
>>>> that possibility. This section discusses how to lower the
>> possibility.
>>>> If people misunderstand the point, I'll clearly say,
>>>>      Regardless whether the explicit tracking function is enabled or
>>>>      not, there are possibilities that a router's membership
>>>>      expectation is inconsistent due to an outdated membership state.
>>>> at the beginning of this section.
>>>
>>> I think there are two issues here:
>>>
>>> The section title is misleading. When I was reading the draft, I got
>>> an impression that explicit tracking function is lowering the
>>> possibility of outdated membership.
>>
>> Ok, then how about, "Lowering the Risk of Wrong Membership
>> Expectation"?
>
> It still does not indicate that we are talking about this when explicit tracking function is enabled. I would like to see something like:
>
> Lowering the Risk of Wrong Membership Expectation with Explicit Tracking function enabled

I think it should be something else. Wrong Membership Expectation sounds
like someone (a person) is expecting the membership to be wrong.

How about say "Lowering the Risk of Wrong Membership State"?

>>> Second issue is that the section also does not clarify this clearly.
>>
>> So as I said how about adding the followin sentence at the beginning
>> of this section?
>>
>>     Regardless whether the explicit tracking function is enabled or
>>     not, there are possibilities that a router's membership
>>     expectation is inconsistent due to an outdated membership state.
>
> Ok. With the above suggested type of title and your suggested text, things will be far more clearer.
>
>>>>> 18. In section 6, should not we talk about how the membership state
>>>>> information is deleted when the version is lowered and the channel
>>>>> is no more required.
>>>>
>>>> Do you mean the following "MAY NOT" is not suitable for this document
>>>> as it's implementation dependent?
>>>> "the router MAY NOT flush the maintained membership state
>> information"
>>>> If so, I could agree. I'll change "MAY NOT" to "may not".

As I wrote in another email today, "MAY NOT" is not defined in 2119, so
whatever we do, all the occurrences of "MAY NOT" need to be replaced
with something else.

>>> I think you did not get my question. Let me rephrase it.
>>>
>>> This draft suggest that router create a new state to explicitly
>>> track the host that are joining a channel. Let us assume that the
>>> host crashed before sending a leave. How and when this new state
>>> maintained in the router is removed?
>>
>> Maybe I don't still understand your question.
>> If you are talking about outdated membership status due to the
>> maintained host crash, the membership status will be updated by
>> general query as mentioned in section 4.
>> If you are talking about the statement of flushing the maintained
>> membership state information in the older version compatibility mode,
>> if you think this behavior is implementation dependend, I'm Ok to
>> remove the statements starting from "On the other hand" in section 6.
>> Or other way you prefer?
>
> I was talking about the first case. I am into implementation. Let me tell you what I think:
>
> 1. The router create this new membership state and keep it updated when it receives reports. The router probably aggregate these reports to create forwarding state.
> 2. This new membership state gets removed if the last host sends a state-change report to leave this channel.
>
> What I am asking is that when is this new membership state removed if the last host has crashed and did not send this state-change report.
>
> Will not we need to link this membership state to the forwarding state router maintains. This way when the group or source timer fires apart from the forwarding state this membership state is also removed. Does this make sense?
>
> The reason for asking this question is that no timer is maintained for this new membership state so there is no way to time out only memership state.
>
>>>>> 19. If we can assume that the robustness count configured in a
>>>>> router truly represents the robustness of that network and if a
>>>>> packet is sent this many times, the intended destination will
>>>>> receive the packet at least once, this whole draft can be
>> simplified
>>>>> a lot. There is no need to generate group or group-source specific
>>>>> queries even when all the hosts have left that channel. I am sure
>>>>> there is something I have missed because this is how fast/immediate
>>>>> leave is implemented for older version of protocols.
>>>>
>>>> I tend to agree, but such protocol tuning is beyond the scope of this
>>>> document.
>>>> Also, we had discussions about specific query suppression in the
>>>> meetings several times. Our consensus was that the specific query
>>>> suppression should be the option (i.e. saying "SHOULD disable this
>>>> specific query suppression" as you see in section 3.2).
>>>
>>> I think its not protocol tuning.

I agree that there is an expectation in the design of IGMP/MLD that
the robustness variable is set appropriately so that unsolicited
reports will make it through. There is always a risk that they won't
though. But one of the benefits of explicit tracking is "fast leave"
which means that you do not need to spend time on a specific query
before you stop forwarding. I don't think the text needs to change
though. It only says that this shouldn't be the default behavior. I
think of this as safety measure, but if you as an operator believe
that your link is fairly robust or that you can configure the
robustness count appropriately so that the chances of unsolicited
messages being lost is sufficiently low, then enabling specific-query
suppression make sense. It depends on the environment whether
fast-leave is important as well.

Stig

>>> A network admin should always know its robustness against unreliable
>>> protocols. So the unsolicited messages should always reach the
>>> router. If we say that there are chances that unsolicited reports
>>> won't reach the router which are sent in multiple than in my
>>> opinion, there is no guarantee that solicited messages will reach
>>> the router.
>>>
>>> This whole concept of explicit tracking function becomes easier if
>>> we follow the above logic.
>>>
>>> Do you see an issue with the above logic?
>>
>> I agree such discussion is interesting, but it is beyond the scope of
>> this document.
>
> I am not sure I understand.
>
>> The solution regarding how the protocol robustness is improved and how
>> the message transmission is guaranteed is not simple. It is not solved
>> only with the explicit tracking function.
>
> I was not talking about how to improve the protocol robustness here.
>
> What I am suggesting is that, with robustness count, things have been working in the field for so many years. So why not make the whole explicit tracking functionality easier by assuming that unsolicited reports are not lost, than what is proposed in this draft?
>
>> I'm happy to work on this topic, but it is not a good idea to discuss
>> such solution in this document.
>> (Note that the IGMP/MLD protocol tuning mainly for wireless and mobile
>> environment is issued in rfc6636 and the more general protocol
>> modification discussion is on going in the Mike's I-D.)
> **************** 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 asaeda@sfc.wide.ad.jp  Wed May  8 18:55:17 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 750B521F902D for <pim@ietfa.amsl.com>; Wed,  8 May 2013 18:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OK21PWin--Be for <pim@ietfa.amsl.com>; Wed,  8 May 2013 18:55:16 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 7391621F902A for <pim@ietf.org>; Wed,  8 May 2013 18:55:15 -0700 (PDT)
Received: from localhost (unknown [133.69.32.86]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id C52C72780A7; Thu,  9 May 2013 10:55:14 +0900 (JST)
Date: Thu, 09 May 2013 10:55:21 +0900 (JST)
Message-Id: <20130509.105521.204388480.asaeda@sfc.wide.ad.jp>
To: stig@venaas.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <518AB9B1.7010601@venaas.com>
References: <20130507.112633.137013197.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com> <518AB9B1.7010601@venaas.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org, bharat_joshi@infosys.com
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 09 May 2013 01:55:17 -0000

> Even though I'm fine with the term "fast leave", I think the abstract
> reads better if it just says:
> 
>    This document describes the IGMP/MLD-based explicit membership
>    tracking function for multicast routers supporting IGMPv3/MLDv2.  The
>    explicit tracking function contributes to saving network resources
>    and shortening leave latency.
> 
> There is no need to introduce any terms in the abstract, the main
> thing
> is that the leave latency is shorter.

Ok, if it is the consensus, I'll just remove that common terminology.

>>> I'll slightly change the sentence as follows;
>>>      ... whenever a router receives the State-Change Report messages
>>>      and changes its router state, it sends the corresponding
>>>      Group-Specific or Group-and-Source Specific Query messages to
>>>      confirm whether or not the report sender is the sole member host.
>>
>> The point I was trying to put across is that "router might send" as it
>> depends upon the state of that channel so the updated sentence still
>> says 'it sends the corresponding' which I feel is not correct.
> 
> I agree this text needs to change. It says "whenever a router receives
> the State-Change Report messages and changes its router state", which
> means that for any such change a specific query is sent. But there are
> state changes where you do not send a specific query. E.g. if a host
> adds a new source (top row in the table in RFC 3376 section 6.4.2), a
> specific query is not sent.

Ok, I understand. How about;
    when a router receives the State-Change Report and needs to
    confirm whether or not the report sender is the sole member host,
    it sends the corresponding Group-Specific or Group-and-Source
    Specific Query messages.

>>>> The section title is misleading. When I was reading the draft, I got
>>>> an impression that explicit tracking function is lowering the
>>>> possibility of outdated membership.
>>>
>>> Ok, then how about, "Lowering the Risk of Wrong Membership
>>> Expectation"?
>>
>> It still does not indicate that we are talking about this when
>> explicit tracking function is enabled. I would like to see something
>> like:
>>
>> Lowering the Risk of Wrong Membership Expectation with Explicit
>> Tracking function enabled
> 
> I think it should be something else. Wrong Membership Expectation
> sounds
> like someone (a person) is expecting the membership to be wrong.
> 
> How about say "Lowering the Risk of Wrong Membership State"?

I can live with that.

>>>>>> 18. In section 6, should not we talk about how the membership state
>>>>>> information is deleted when the version is lowered and the channel
>>>>>> is no more required.
>>>>>
>>>>> Do you mean the following "MAY NOT" is not suitable for this document
>>>>> as it's implementation dependent?
>>>>> "the router MAY NOT flush the maintained membership state
>>> information"
>>>>> If so, I could agree. I'll change "MAY NOT" to "may not".
> 
> As I wrote in another email today, "MAY NOT" is not defined in 2119,
> so
> whatever we do, all the occurrences of "MAY NOT" need to be replaced
> with something else.

Ok, only these two parts use MAY NOT. I'll change them to "may not".

>>>>> I tend to agree, but such protocol tuning is beyond the scope of this
>>>>> document.
>>>>> Also, we had discussions about specific query suppression in the
>>>>> meetings several times. Our consensus was that the specific query
>>>>> suppression should be the option (i.e. saying "SHOULD disable this
>>>>> specific query suppression" as you see in section 3.2).
> 
> I agree that there is an expectation in the design of IGMP/MLD that
> the robustness variable is set appropriately so that unsolicited
> reports will make it through. There is always a risk that they won't
> though. But one of the benefits of explicit tracking is "fast leave"
> which means that you do not need to spend time on a specific query
> before you stop forwarding. I don't think the text needs to change
> though. It only says that this shouldn't be the default behavior. I
> think of this as safety measure, but if you as an operator believe
> that your link is fairly robust or that you can configure the
> robustness count appropriately so that the chances of unsolicited
> messages being lost is sufficiently low, then enabling specific-query
> suppression make sense. It depends on the environment whether
> fast-leave is important as well.

I completely agree to this explanation.
I'll add some text. Thanks.

Regards,
--
Hitoshi Asaeda

From asaeda@sfc.wide.ad.jp  Wed May  8 19:01:07 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAFDC21F86D9 for <pim@ietfa.amsl.com>; Wed,  8 May 2013 19:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ia6n5HkqIEUH for <pim@ietfa.amsl.com>; Wed,  8 May 2013 19:01:07 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 6D67321F850B for <pim@ietf.org>; Wed,  8 May 2013 19:01:06 -0700 (PDT)
Received: from localhost (unknown [133.69.32.86]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 11F042780A7; Thu,  9 May 2013 11:01:06 +0900 (JST)
Date: Thu, 09 May 2013 11:01:22 +0900 (JST)
Message-Id: <20130509.110122.80634049.asaeda@sfc.wide.ad.jp>
To: stig@venaas.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130509.105521.204388480.asaeda@sfc.wide.ad.jp>
References: <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com> <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 09 May 2013 02:01:08 -0000

> Ok, I understand. How about;
>     when a router receives the State-Change Report and needs to
>     confirm whether or not the report sender is the sole member host,
>     it sends the corresponding Group-Specific or Group-and-Source
>     Specific Query messages.

A little change.
   when a router receives the State-Change Report and needs to confirm
   whether or not the report sender is the sole member host for the
   received record(s), it sends the corresponding Group-Specific or
   Group-and-Source Specific Query messages.

Regards,
--
Hitoshi Asaeda

From stig@venaas.com  Wed May  8 20:31:07 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40ADE21F8624 for <pim@ietfa.amsl.com>; Wed,  8 May 2013 20:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGWqCbqRPNXr for <pim@ietfa.amsl.com>; Wed,  8 May 2013 20:31:06 -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 05C8321F8606 for <pim@ietf.org>; Wed,  8 May 2013 20:31:05 -0700 (PDT)
Received: from [192.168.1.101] (c-67-170-194-177.hsd1.ca.comcast.net [67.170.194.177]) by ufisa.uninett.no (Postfix) with ESMTPSA id 70ABF8104; Thu,  9 May 2013 05:31:01 +0200 (CEST)
Message-ID: <518B1981.8000703@venaas.com>
Date: Wed, 08 May 2013 20:35:29 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
References: <20130507.112633.137013197.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com> <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130509.105521.204388480.asaeda@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org, bharat_joshi@infosys.com
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 09 May 2013 03:31:07 -0000

On 08.05.2013 18:55, Hitoshi Asaeda wrote:
>> Even though I'm fine with the term "fast leave", I think the abstract
>> reads better if it just says:
>>
>>     This document describes the IGMP/MLD-based explicit membership
>>     tracking function for multicast routers supporting IGMPv3/MLDv2.  The
>>     explicit tracking function contributes to saving network resources
>>     and shortening leave latency.
>>
>> There is no need to introduce any terms in the abstract, the main
>> thing
>> is that the leave latency is shorter.
>
> Ok, if it is the consensus, I'll just remove that common terminology.

I don't know if it is consensus and it doesn't really matter to me. But
I think it reads better this way. If you prefer having "fast leave"
there, that is fine with me too.

Your proposed change regarding State-Change in the email you sent after
this one looks good to me.

Stig

>>>> I'll slightly change the sentence as follows;
>>>>       ... whenever a router receives the State-Change Report messages
>>>>       and changes its router state, it sends the corresponding
>>>>       Group-Specific or Group-and-Source Specific Query messages to
>>>>       confirm whether or not the report sender is the sole member host.
>>>
>>> The point I was trying to put across is that "router might send" as it
>>> depends upon the state of that channel so the updated sentence still
>>> says 'it sends the corresponding' which I feel is not correct.
>>
>> I agree this text needs to change. It says "whenever a router receives
>> the State-Change Report messages and changes its router state", which
>> means that for any such change a specific query is sent. But there are
>> state changes where you do not send a specific query. E.g. if a host
>> adds a new source (top row in the table in RFC 3376 section 6.4.2), a
>> specific query is not sent.
>
> Ok, I understand. How about;
>      when a router receives the State-Change Report and needs to
>      confirm whether or not the report sender is the sole member host,
>      it sends the corresponding Group-Specific or Group-and-Source
>      Specific Query messages.
>
>>>>> The section title is misleading. When I was reading the draft, I got
>>>>> an impression that explicit tracking function is lowering the
>>>>> possibility of outdated membership.
>>>>
>>>> Ok, then how about, "Lowering the Risk of Wrong Membership
>>>> Expectation"?
>>>
>>> It still does not indicate that we are talking about this when
>>> explicit tracking function is enabled. I would like to see something
>>> like:
>>>
>>> Lowering the Risk of Wrong Membership Expectation with Explicit
>>> Tracking function enabled
>>
>> I think it should be something else. Wrong Membership Expectation
>> sounds
>> like someone (a person) is expecting the membership to be wrong.
>>
>> How about say "Lowering the Risk of Wrong Membership State"?
>
> I can live with that.
>
>>>>>>> 18. In section 6, should not we talk about how the membership state
>>>>>>> information is deleted when the version is lowered and the channel
>>>>>>> is no more required.
>>>>>>
>>>>>> Do you mean the following "MAY NOT" is not suitable for this document
>>>>>> as it's implementation dependent?
>>>>>> "the router MAY NOT flush the maintained membership state
>>>> information"
>>>>>> If so, I could agree. I'll change "MAY NOT" to "may not".
>>
>> As I wrote in another email today, "MAY NOT" is not defined in 2119,
>> so
>> whatever we do, all the occurrences of "MAY NOT" need to be replaced
>> with something else.
>
> Ok, only these two parts use MAY NOT. I'll change them to "may not".
>
>>>>>> I tend to agree, but such protocol tuning is beyond the scope of this
>>>>>> document.
>>>>>> Also, we had discussions about specific query suppression in the
>>>>>> meetings several times. Our consensus was that the specific query
>>>>>> suppression should be the option (i.e. saying "SHOULD disable this
>>>>>> specific query suppression" as you see in section 3.2).
>>
>> I agree that there is an expectation in the design of IGMP/MLD that
>> the robustness variable is set appropriately so that unsolicited
>> reports will make it through. There is always a risk that they won't
>> though. But one of the benefits of explicit tracking is "fast leave"
>> which means that you do not need to spend time on a specific query
>> before you stop forwarding. I don't think the text needs to change
>> though. It only says that this shouldn't be the default behavior. I
>> think of this as safety measure, but if you as an operator believe
>> that your link is fairly robust or that you can configure the
>> robustness count appropriately so that the chances of unsolicited
>> messages being lost is sufficiently low, then enabling specific-query
>> suppression make sense. It depends on the environment whether
>> fast-leave is important as well.
>
> I completely agree to this explanation.
> I'll add some text. Thanks.
>
> Regards,
> --
> Hitoshi Asaeda
>


From asaeda@sfc.wide.ad.jp  Wed May  8 21:37:47 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4236C21F9021 for <pim@ietfa.amsl.com>; Wed,  8 May 2013 21:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJONvlqZRTvv for <pim@ietfa.amsl.com>; Wed,  8 May 2013 21:37:46 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id A750821F901A for <pim@ietf.org>; Wed,  8 May 2013 21:37:45 -0700 (PDT)
Received: from localhost (unknown [133.69.32.86]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 3D3442780A7; Thu,  9 May 2013 13:37:44 +0900 (JST)
Date: Thu, 09 May 2013 13:37:50 +0900 (JST)
Message-Id: <20130509.133750.135894423.asaeda@sfc.wide.ad.jp>
To: stig@venaas.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <518B1981.8000703@venaas.com>
References: <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp> <518B1981.8000703@venaas.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 09 May 2013 04:37:47 -0000

>>>     This document describes the IGMP/MLD-based explicit membership
>>>     tracking function for multicast routers supporting IGMPv3/MLDv2.  The
>>>     explicit tracking function contributes to saving network resources
>>>     and shortening leave latency.
>>>
>>> There is no need to introduce any terms in the abstract, the main
>>> thing
>>> is that the leave latency is shorter.
>>
>> Ok, if it is the consensus, I'll just remove that common terminology.
> 
> I don't know if it is consensus and it doesn't really matter to
> me. But
> I think it reads better this way. If you prefer having "fast leave"
> there, that is fine with me too.

I've thought "fast leave" is easy for readers to recognize the benefit
of this function and can become the index of this doc, but if no
preference, I'll remove it.

> Your proposed change regarding State-Change in the email you sent
> after
> this one looks good to me.

Thanks for your input.

Regards,
--
Hitoshi Asaeda

From eckert@cisco.com  Thu May  9 07:09:36 2013
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB9C21F8DD5 for <pim@ietfa.amsl.com>; Thu,  9 May 2013 07:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAdJu+3eNtDn for <pim@ietfa.amsl.com>; Thu,  9 May 2013 07:09:32 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 03FE521F89AF for <pim@ietf.org>; Thu,  9 May 2013 07:09:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5791; q=dns/txt; s=iport; t=1368108572; x=1369318172; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=cA1aKxRYLktTopMVRLMqNawg6F7pRUjiJ4+vff/lHZ4=; b=W6yGvLYjkQlGmNqGjvSPdXYnX2Ngsse3sIJM0tp9WUCx9spjQ7FvMBx/ QXIxrXpUNHXAZBPbslQbT/+yNr+zf+VClOOFIajX4nyfZbKGyeeErOksE Q0JK2YeXSubYzTr17Y7OAnAujyolSrLw1PQlAtw4ZK53hoQnpDN99iyPQ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAJeti1GrRDoI/2dsb2JhbABSgwc3wAd6FnSCHwEBAQQBAQE3NAsQCxIGCSUPBRMiFBOICw29OASNZoFCB4NVA4kajhEBiiWHEIMvHIE2
X-IronPort-AV: E=Sophos;i="4.87,641,1363132800"; d="scan'208";a="78122023"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 09 May 2013 14:09:31 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r49E9U1B031556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 May 2013 14:09:30 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r49E9SPC015686;  Thu, 9 May 2013 07:09:28 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r49E9RRV015683; Thu, 9 May 2013 07:09:27 -0700
Date: Thu, 9 May 2013 07:09:27 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Stig Venaas <stig@venaas.com>
Message-ID: <20130509140926.GP12184@cisco.com>
References: <20130507.112633.137013197.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com> <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp> <518B1981.8000703@venaas.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <518B1981.8000703@venaas.com>
User-Agent: Mutt/1.4.2.2i
Cc: bharat_joshi@infosys.com, pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 09 May 2013 14:09:36 -0000

While we're nitpicking

 ...
 contributes to saving network resources, shortening leave latency and
 enables operators to see which downstream routers(s) on a LAN are
 joined to which multicast tree.

Just saying. ;-)

On Wed, May 08, 2013 at 08:35:29PM -0700, Stig Venaas wrote:
> On 08.05.2013 18:55, Hitoshi Asaeda wrote:
> >>Even though I'm fine with the term "fast leave", I think the abstract
> >>reads better if it just says:
> >>
> >>    This document describes the IGMP/MLD-based explicit membership
> >>    tracking function for multicast routers supporting IGMPv3/MLDv2.  The
> >>    explicit tracking function contributes to saving network resources
> >>    and shortening leave latency.
> >>
> >>There is no need to introduce any terms in the abstract, the main
> >>thing
> >>is that the leave latency is shorter.
> >
> >Ok, if it is the consensus, I'll just remove that common terminology.
> 
> I don't know if it is consensus and it doesn't really matter to me. But
> I think it reads better this way. If you prefer having "fast leave"
> there, that is fine with me too.
> 
> Your proposed change regarding State-Change in the email you sent after
> this one looks good to me.
> 
> Stig
> 
> >>>>I'll slightly change the sentence as follows;
> >>>>      ... whenever a router receives the State-Change Report messages
> >>>>      and changes its router state, it sends the corresponding
> >>>>      Group-Specific or Group-and-Source Specific Query messages to
> >>>>      confirm whether or not the report sender is the sole member host.
> >>>
> >>>The point I was trying to put across is that "router might send" as it
> >>>depends upon the state of that channel so the updated sentence still
> >>>says 'it sends the corresponding' which I feel is not correct.
> >>
> >>I agree this text needs to change. It says "whenever a router receives
> >>the State-Change Report messages and changes its router state", which
> >>means that for any such change a specific query is sent. But there are
> >>state changes where you do not send a specific query. E.g. if a host
> >>adds a new source (top row in the table in RFC 3376 section 6.4.2), a
> >>specific query is not sent.
> >
> >Ok, I understand. How about;
> >     when a router receives the State-Change Report and needs to
> >     confirm whether or not the report sender is the sole member host,
> >     it sends the corresponding Group-Specific or Group-and-Source
> >     Specific Query messages.
> >
> >>>>>The section title is misleading. When I was reading the draft, I got
> >>>>>an impression that explicit tracking function is lowering the
> >>>>>possibility of outdated membership.
> >>>>
> >>>>Ok, then how about, "Lowering the Risk of Wrong Membership
> >>>>Expectation"?
> >>>
> >>>It still does not indicate that we are talking about this when
> >>>explicit tracking function is enabled. I would like to see something
> >>>like:
> >>>
> >>>Lowering the Risk of Wrong Membership Expectation with Explicit
> >>>Tracking function enabled
> >>
> >>I think it should be something else. Wrong Membership Expectation
> >>sounds
> >>like someone (a person) is expecting the membership to be wrong.
> >>
> >>How about say "Lowering the Risk of Wrong Membership State"?
> >
> >I can live with that.
> >
> >>>>>>>18. In section 6, should not we talk about how the membership state
> >>>>>>>information is deleted when the version is lowered and the channel
> >>>>>>>is no more required.
> >>>>>>
> >>>>>>Do you mean the following "MAY NOT" is not suitable for this document
> >>>>>>as it's implementation dependent?
> >>>>>>"the router MAY NOT flush the maintained membership state
> >>>>information"
> >>>>>>If so, I could agree. I'll change "MAY NOT" to "may not".
> >>
> >>As I wrote in another email today, "MAY NOT" is not defined in 2119,
> >>so
> >>whatever we do, all the occurrences of "MAY NOT" need to be replaced
> >>with something else.
> >
> >Ok, only these two parts use MAY NOT. I'll change them to "may not".
> >
> >>>>>>I tend to agree, but such protocol tuning is beyond the scope of this
> >>>>>>document.
> >>>>>>Also, we had discussions about specific query suppression in the
> >>>>>>meetings several times. Our consensus was that the specific query
> >>>>>>suppression should be the option (i.e. saying "SHOULD disable this
> >>>>>>specific query suppression" as you see in section 3.2).
> >>
> >>I agree that there is an expectation in the design of IGMP/MLD that
> >>the robustness variable is set appropriately so that unsolicited
> >>reports will make it through. There is always a risk that they won't
> >>though. But one of the benefits of explicit tracking is "fast leave"
> >>which means that you do not need to spend time on a specific query
> >>before you stop forwarding. I don't think the text needs to change
> >>though. It only says that this shouldn't be the default behavior. I
> >>think of this as safety measure, but if you as an operator believe
> >>that your link is fairly robust or that you can configure the
> >>robustness count appropriately so that the chances of unsolicited
> >>messages being lost is sufficiently low, then enabling specific-query
> >>suppression make sense. It depends on the environment whether
> >>fast-leave is important as well.
> >
> >I completely agree to this explanation.
> >I'll add some text. Thanks.
> >
> >Regards,
> >--
> >Hitoshi Asaeda
> >
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From mmcbride7@gmail.com  Thu May  9 12:48:19 2013
Return-Path: <mmcbride7@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F58121F914C for <pim@ietfa.amsl.com>; Thu,  9 May 2013 12:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BB40mzIx8GdJ for <pim@ietfa.amsl.com>; Thu,  9 May 2013 12:48:18 -0700 (PDT)
Received: from mail-da0-x22b.google.com (mail-da0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A020E21F9164 for <pim@ietf.org>; Thu,  9 May 2013 12:48:17 -0700 (PDT)
Received: by mail-da0-f43.google.com with SMTP id u7so1797390dae.16 for <pim@ietf.org>; Thu, 09 May 2013 12:48:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=IVq1oaxobYsmJ83WJQFYdQ0rK4Vl/0L+C31ogEBZ/xI=; b=eOs5UEQnoBSIq93izMiEkfDH5r05IsXZE76eI6y9bOt63AKTNayIfKrHfprKkzNBfF +OXDI1efTgD0EobrXbR+9ouetsYs/HIZL2uAUswMaF+vLPT4P/w0h4Us9ZLcu67MZScr sKQcInEIXtP3sM+bpKBilVR/2U1K+WOwx/Frbs37YkgTCQEr9wY0OBt2X4eq4iJWBR0Y +2HDAfwDi9nA1BBxkLr3tnRKLgolcZQqq8wEFFvxa0meoEjvvrMmUQuO7e/qz4gSPO6N YgtVyOSm4R+1CSaLtBGJZOQPBNhEsSW/B7Sw/EGZCF2DszUct0x7yje98A9NoF4iVSRs TGWg==
MIME-Version: 1.0
X-Received: by 10.66.235.3 with SMTP id ui3mr14699282pac.200.1368128897362; Thu, 09 May 2013 12:48:17 -0700 (PDT)
Received: by 10.68.209.167 with HTTP; Thu, 9 May 2013 12:48:17 -0700 (PDT)
Date: Thu, 9 May 2013 12:48:17 -0700
Message-ID: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: pim@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 09 May 2013 19:48:19 -0000

draft-zhou-pim-vrrp-01 was presented in our most recent pim meeting in
Orlando. 4 people were in favor of adopting the draft. Zero against.
Please read the draft (its short) and provide an opinion either way by
the end of next Friday the 17th.

http://www.ietf.org/id/draft-zhou-pim-vrrp-01.txt

thanks,
mike

From xuxiaohu@huawei.com  Thu May  9 19:32:43 2013
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C9E21F8FF0 for <pim@ietfa.amsl.com>; Thu,  9 May 2013 19:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level: 
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGFxvZWeRYeP for <pim@ietfa.amsl.com>; Thu,  9 May 2013 19:32:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4885821F8C7D for <pim@ietf.org>; Thu,  9 May 2013 19:32:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ASQ82497; Fri, 10 May 2013 02:32:39 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 10 May 2013 03:32:28 +0100
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 10 May 2013 03:32:38 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.243]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.01.0323.007; Fri, 10 May 2013 10:32:32 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOTO46Kv7cKrIMmE+yfb3Ht5i9dJj9sx9A
Date: Fri, 10 May 2013 02:32:32 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com>
In-Reply-To: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 10 May 2013 02:32:44 -0000

SGkgYWxsLA0KDQpUaGlzIGRyYWZ0IHJlbWluZHMgbWUgdGhhdCB0aGVyZSBoYXMgYmVlbiBhIGRy
YWZ0IChodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14dS1waW0tZHJwcmlvcml0eS1h
dXRvLWFkanVzdG1lbnQtMDMpIHRocmVlIHllYXJzIGJlZm9yZSB3aGljaCB1c2VzIGFsbW9zdCB0
aGUgc2FtZSB0ZWNobm9sb2d5IHRvIHNhdmUgYWxtb3N0IHRoZSBzYW1lIHByb2JsZW0uDQoNClRo
ZSBmb2xsb3dpbmcgaXMgcXVvdGVkIGZyb20gdGhlIGFib3ZlIGRyYWZ0Og0KDQogICAiSW4gZmFj
dCwgaWYgVlJSUCBpcyBydW4gb24gdGhlIFBJTSByb3V0ZXJzIGFuZCB0aGUgVlJSUCBoYXMgZW5h
YmxlZA0KICAgdGhlIHVwc3RyZWFtIGxpbmsgdHJhY2tpbmcgbWVjaGFuaXNtLCB0aGUgUElNIERS
IGZhaWxvdmVyIG1lY2hhbmlzbQ0KICAgY291bGQgYmUgY291cGxlZCB3aXRoIHRoZSBWUlJQIHNv
IGFzIHRvIHJldXNlIHRoZSB1cHN0cmVhbSBsaW5rDQogICB0cmFja2luZyBtZWNoYW5pc20gb2Yg
VlJSUC4gT25lIG9wdGlvbiBpcyB0byBzeW5jaHJvbml6ZSB0aGUgUElNIERSDQogICBwcmlvcml0
eSB2YWx1ZSB0byB0aGUgVlJSUCBwcmlvcml0eSB2YWx1ZSBhbHdheXMuIEluIHRoaXMgd2F5LCB0
aGUNCiAgIFBJTSBEUiBhbmQgdGhlIFZSUlAgbWFzdGVyIHdpbGwgYWx3YXlzIHJ1biBvbiBhbiBp
ZGVudGljYWwgcm91dGVyIGlmDQogICB0aGUgVlJSUCBQcmVlbXB0X01vZGUgaXMgc2V0IHRvIFRy
dWUuIEFub3RoZXIgb3B0aW9uIGlzIHRvIG1ha2UgdGhlDQogICBQSU0gRFIgYW5kIHRoZSBWUlJQ
IG1hc3RlciBydW4gb24gYW4gaWRlbnRpY2FsIHJvdXRlciBhbnl3YXkgKGkuZS4sDQogICByZWdh
cmRsZXNzIHdoZXRoZXIgb3Igbm90IHRoZSBWUlJQIFByZWVtcHRfTW9kZSBpcyBUcnVlKS4gVG8g
YWNoaWV2ZQ0KICAgdGhpcyBnb2FsLCB0aGUgUElNIERSIHByaW9yaXR5IG9mIHRoZSBWUlJQIG1h
c3RlciByb3V0ZXIgU0hPVUxEDQogICBhbHdheXMgYmUgc2V0IHRvIGEgaGlnaGVyIGZpeGVkIHZh
bHVlIHRoYW4gdGhhdCBvZiB0aGUgVlJSUCBzbGF2ZQ0KICAgcm91dGVyIGF1dG9tYXRpY2FsbHku
Ig0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8
/sjLOiBwaW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnBpbS1ib3VuY2VzQGlldGYub3JnXSC0
+rHtIE1pa2UNCj4gTWNCcmlkZQ0KPiC3osvNyrG85DogMjAxM8TqNdTCMTDI1SAzOjQ4DQo+IMrV
vP7IyzogcGltQGlldGYub3JnDQo+INb3zOI6IFtwaW1dIGNhbGwgZm9yIGFkb3B0aW9uOiBkcmFm
dC16aG91LXBpbS12cnJwLTAxDQo+IA0KPiBkcmFmdC16aG91LXBpbS12cnJwLTAxIHdhcyBwcmVz
ZW50ZWQgaW4gb3VyIG1vc3QgcmVjZW50IHBpbSBtZWV0aW5nIGluDQo+IE9ybGFuZG8uIDQgcGVv
cGxlIHdlcmUgaW4gZmF2b3Igb2YgYWRvcHRpbmcgdGhlIGRyYWZ0LiBaZXJvIGFnYWluc3QuDQo+
IFBsZWFzZSByZWFkIHRoZSBkcmFmdCAoaXRzIHNob3J0KSBhbmQgcHJvdmlkZSBhbiBvcGluaW9u
IGVpdGhlciB3YXkgYnkNCj4gdGhlIGVuZCBvZiBuZXh0IEZyaWRheSB0aGUgMTd0aC4NCj4gDQo+
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtemhvdS1waW0tdnJycC0wMS50eHQNCj4gDQo+
IHRoYW5rcywNCj4gbWlrZQ0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPiBwaW0gbWFpbGluZyBsaXN0DQo+IHBpbUBpZXRmLm9yZw0KPiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbQ0K

From stig@venaas.com  Fri May 10 10:32:03 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E8921F8C1A for <pim@ietfa.amsl.com>; Fri, 10 May 2013 10:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3TCseN5YSgam for <pim@ietfa.amsl.com>; Fri, 10 May 2013 10:32:02 -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 A3BC921F89B2 for <pim@ietf.org>; Fri, 10 May 2013 10:32:02 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 1FD8E8219; Fri, 10 May 2013 19:31:58 +0200 (CEST)
Message-ID: <518D2F0C.8030805@venaas.com>
Date: Fri, 10 May 2013 10:31:56 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
References: <20130507.112633.137013197.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com> <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130509.105521.204388480.asaeda@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org, bharat_joshi@infosys.com
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 10 May 2013 17:32:03 -0000

On 5/8/2013 6:55 PM, Hitoshi Asaeda wrote:
[...]
>>>>>> I tend to agree, but such protocol tuning is beyond the scope of this
>>>>>> document.
>>>>>> Also, we had discussions about specific query suppression in the
>>>>>> meetings several times. Our consensus was that the specific query
>>>>>> suppression should be the option (i.e. saying "SHOULD disable this
>>>>>> specific query suppression" as you see in section 3.2).
>>
>> I agree that there is an expectation in the design of IGMP/MLD that
>> the robustness variable is set appropriately so that unsolicited
>> reports will make it through. There is always a risk that they won't
>> though. But one of the benefits of explicit tracking is "fast leave"
>> which means that you do not need to spend time on a specific query
>> before you stop forwarding. I don't think the text needs to change
>> though. It only says that this shouldn't be the default behavior. I
>> think of this as safety measure, but if you as an operator believe
>> that your link is fairly robust or that you can configure the
>> robustness count appropriately so that the chances of unsolicited
>> messages being lost is sufficiently low, then enabling specific-query
>> suppression make sense. It depends on the environment whether
>> fast-leave is important as well.
>
> I completely agree to this explanation.
> I'll add some text. Thanks.

I have one concern here. I noticed that the specific query suppression
text says:

    Specific or Group-and-Source Specific Query messages transmitted from
    a router, and reduce the number of Current-State Report messages
    transmitted from member hosts.  If a router enables the explicit
    tracking function with "specific query suppression", it suppresses
    specific query transmission and transmits specific query messages
    only when the router expects that the State-Change Report sender is
    the sole member of the channel, based on its membership state
    information (expressed in Section 3.1).

I believe it is fairly common to also suppress specific query when the
last member is leaving, in order to do "fast-leave". Basically stopping
forwarding without having to wait for responses to specific queries.

I vaguely remember we discussed this a couple of years ago...

I was thinking of this when I wrote "fast-leave" above. If you can
expect the robustness to be tuned appropriately, this should be
fairly safe. See what I wrote regarding tradeoff above.

I think Bharat was mentioning this as well, although I'm not quite sure
if I got his point.

Stig

> Regards,
> --
> Hitoshi Asaeda
>


From hou@cisco.com  Fri May 10 11:36:33 2013
Return-Path: <hou@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 101CF21F901D for <pim@ietfa.amsl.com>; Fri, 10 May 2013 11:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bt0B2Bmqy19P for <pim@ietfa.amsl.com>; Fri, 10 May 2013 11:36:28 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E602121F86F4 for <pim@ietf.org>; Fri, 10 May 2013 11:36:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=569; q=dns/txt; s=iport; t=1368210988; x=1369420588; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=CHiNl67nQgxmIPlfQejcgQOeIOWOomLqU7G5Rw2yCsQ=; b=SELN6pW4Vi3OnrlGtFW9ixgBv9Qd59MCjmchxQxFH4DdKrRc1k+VN6Ix I8cvrRg1vtESpB7O9ACr3AC0gaDxghnmxpI+Ux5Dpol7192+1xSP+lH+7 wab+L4Jz5hLPwmq8cuDa2SWzHVwB2DRDVBU7DWn6Ku15Y8C6z/nmPYkOy I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjAFAH89jVGtJXHA/2dsb2JhbABSgwc3gnW9JnwWdIIhAQQBAQEaHTQdAQgiFDEGCyUCBAESCAGHcQMPDLU5DYgijFKCJTiCdGEDlUiNd4Uigw+CJw
X-IronPort-AV: E=Sophos;i="4.87,650,1363132800"; d="scan'208";a="205966752"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-9.cisco.com with ESMTP; 10 May 2013 18:36:27 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r4AIaRZR022659 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 10 May 2013 18:36:27 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.154]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Fri, 10 May 2013 13:36:27 -0500
From: "Heidi Ou (hou)" <hou@cisco.com>
To: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOTO4u4yNDvIZCxE6+tbB0bFMjrJj+nyYA
Date: Fri, 10 May 2013 18:36:26 +0000
Message-ID: <716547F7B399274C9FE8C1CFBC6C95C911369AC7@xmb-rcd-x06.cisco.com>
In-Reply-To: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [128.107.163.99]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3C9CE460F11B22438E8274A68D82F54D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 10 May 2013 18:36:33 -0000

I support adoption of the draft.

- Heidi

On 5/9/13 12:48 PM, "Mike McBride" <mmcbride7@gmail.com> wrote:

>draft-zhou-pim-vrrp-01 was presented in our most recent pim meeting in
>Orlando. 4 people were in favor of adopting the draft. Zero against.
>Please read the draft (its short) and provide an opinion either way by
>the end of next Friday the 17th.
>
>http://www.ietf.org/id/draft-zhou-pim-vrrp-01.txt
>
>thanks,
>mike
>_______________________________________________
>pim mailing list
>pim@ietf.org
>https://www.ietf.org/mailman/listinfo/pim


From xuxiaohu@huawei.com  Thu May  9 19:27:37 2013
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C8521F8ED8 for <pim@ietfa.amsl.com>; Thu,  9 May 2013 19:27:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level: 
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oG6kZnC3xLF7 for <pim@ietfa.amsl.com>; Thu,  9 May 2013 19:27:33 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A9B4721F85C3 for <pim@ietf.org>; Thu,  9 May 2013 19:27:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARF94120; Fri, 10 May 2013 02:27:31 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 10 May 2013 03:27:20 +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.1.323.7; Fri, 10 May 2013 10:27:29 +0800
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.243]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.01.0323.007; Fri, 10 May 2013 10:27:23 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Mike McBride <mmcbride7@gmail.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOTO46Kv7cKrIMmE+yfb3Ht5i9dJj9qGeQ
Date: Fri, 10 May 2013 02:27:23 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F6699F@NKGEML512-MBS.china.huawei.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com>
In-Reply-To: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 10 May 2013 13:08:55 -0700
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 10 May 2013 02:27:37 -0000

SGkgYWxsLA0KDQpUaGlzIGRyYWZ0IHJlbWluZHMgbWUgdGhhdCB0aGVyZSBoYXMgYmVlbiBhIGRy
YWZ0IChodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14dS1waW0tZHJwcmlvcml0eS1h
dXRvLWFkanVzdG1lbnQtMDMpIHRocmVlIHllYXJzIGJlZm9yZSB3aGljaCB1c2VzIGFsbW9zdCB0
aGUgc2FtZSB0ZWNobm9sb2d5IHRvIHNhdmUgYWxtb3N0IHRoZSBzYW1lIHByb2JsZW0uDQoNClRo
ZSBmb2xsb3dpbmcgaXMgcXVvdGVkIGZyb20gdGhlIGFib3ZlIGRyYWZ0Og0KDQogICAiSW4gZmFj
dCwgaWYgVlJSUCBpcyBydW4gb24gdGhlIFBJTSByb3V0ZXJzIGFuZCB0aGUgVlJSUCBoYXMgZW5h
YmxlZA0KICAgdGhlIHVwc3RyZWFtIGxpbmsgdHJhY2tpbmcgbWVjaGFuaXNtLCB0aGUgUElNIERS
IGZhaWxvdmVyIG1lY2hhbmlzbQ0KICAgY291bGQgYmUgY291cGxlZCB3aXRoIHRoZSBWUlJQIHNv
IGFzIHRvIHJldXNlIHRoZSB1cHN0cmVhbSBsaW5rDQogICB0cmFja2luZyBtZWNoYW5pc20gb2Yg
VlJSUC4gT25lIG9wdGlvbiBpcyB0byBzeW5jaHJvbml6ZSB0aGUgUElNIERSDQogICBwcmlvcml0
eSB2YWx1ZSB0byB0aGUgVlJSUCBwcmlvcml0eSB2YWx1ZSBhbHdheXMuIEluIHRoaXMgd2F5LCB0
aGUNCiAgIFBJTSBEUiBhbmQgdGhlIFZSUlAgbWFzdGVyIHdpbGwgYWx3YXlzIHJ1biBvbiBhbiBp
ZGVudGljYWwgcm91dGVyIGlmDQogICB0aGUgVlJSUCBQcmVlbXB0X01vZGUgaXMgc2V0IHRvIFRy
dWUuIEFub3RoZXIgb3B0aW9uIGlzIHRvIG1ha2UgdGhlDQogICBQSU0gRFIgYW5kIHRoZSBWUlJQ
IG1hc3RlciBydW4gb24gYW4gaWRlbnRpY2FsIHJvdXRlciBhbnl3YXkgKGkuZS4sDQogICByZWdh
cmRsZXNzIHdoZXRoZXIgb3Igbm90IHRoZSBWUlJQIFByZWVtcHRfTW9kZSBpcyBUcnVlKS4gVG8g
YWNoaWV2ZQ0KICAgdGhpcyBnb2FsLCB0aGUgUElNIERSIHByaW9yaXR5IG9mIHRoZSBWUlJQIG1h
c3RlciByb3V0ZXIgU0hPVUxEDQogICBhbHdheXMgYmUgc2V0IHRvIGEgaGlnaGVyIGZpeGVkIHZh
bHVlIHRoYW4gdGhhdCBvZiB0aGUgVlJSUCBzbGF2ZQ0KICAgcm91dGVyIGF1dG9tYXRpY2FsbHku
Ig0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8
/sjLOiBwaW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnBpbS1ib3VuY2VzQGlldGYub3JnXSC0
+rHtIE1pa2UNCj4gTWNCcmlkZQ0KPiC3osvNyrG85DogMjAxM8TqNdTCMTDI1SAzOjQ4DQo+IMrV
vP7IyzogcGltQGlldGYub3JnDQo+INb3zOI6IFtwaW1dIGNhbGwgZm9yIGFkb3B0aW9uOiBkcmFm
dC16aG91LXBpbS12cnJwLTAxDQo+IA0KPiBkcmFmdC16aG91LXBpbS12cnJwLTAxIHdhcyBwcmVz
ZW50ZWQgaW4gb3VyIG1vc3QgcmVjZW50IHBpbSBtZWV0aW5nIGluDQo+IE9ybGFuZG8uIDQgcGVv
cGxlIHdlcmUgaW4gZmF2b3Igb2YgYWRvcHRpbmcgdGhlIGRyYWZ0LiBaZXJvIGFnYWluc3QuDQo+
IFBsZWFzZSByZWFkIHRoZSBkcmFmdCAoaXRzIHNob3J0KSBhbmQgcHJvdmlkZSBhbiBvcGluaW9u
IGVpdGhlciB3YXkgYnkNCj4gdGhlIGVuZCBvZiBuZXh0IEZyaWRheSB0aGUgMTd0aC4NCj4gDQo+
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtemhvdS1waW0tdnJycC0wMS50eHQNCj4gDQo+
IHRoYW5rcywNCj4gbWlrZQ0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPiBwaW0gbWFpbGluZyBsaXN0DQo+IHBpbUBpZXRmLm9yZw0KPiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BpbQ0K

From adrian@olddog.co.uk  Sat May 11 09:37:09 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7508C21F8D8E for <pim@ietfa.amsl.com>; Sat, 11 May 2013 09:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.577
X-Spam-Level: 
X-Spam-Status: No, score=-2.577 tagged_above=-999 required=5 tests=[AWL=0.022,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JCHmAs16wVH4 for <pim@ietfa.amsl.com>; Sat, 11 May 2013 09:37:04 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACC421F8D6A for <pim@ietf.org>; Sat, 11 May 2013 09:37:00 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4BGatsF005023;  Sat, 11 May 2013 17:36:55 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4BGasr4005013 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 11 May 2013 17:36:54 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pim@ietf.org>
Date: Sat, 11 May 2013 17:36:53 +0100
Message-ID: <03ca01ce4e65$bf4c11a0$3de434e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5OZZUSKecjjEFHTH+ZKnOxicQKfA==
Content-Language: en-gb
Cc: 'Brian Haberman' <brian@innovationslab.net>, holbrook@arastra.com, bcain99@gmail.com
Subject: [pim] Trying to clean-up an SSM Errata Report
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 11 May 2013 16:37:09 -0000

Hi,

Take a look at http://www.rfc-editor.org/errata_search.php?eid=905

I can't make head or tail of what the appropriate resolution is. Advice please.

And any ideas if there is a better place to discuss this.

Thanks,
Adrian


From eckert@cisco.com  Sat May 11 11:26:05 2013
Return-Path: <eckert@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62FE21F8574; Sat, 11 May 2013 11:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.593
X-Spam-Level: 
X-Spam-Status: No, score=-9.593 tagged_above=-999 required=5 tests=[AWL=-1.006, BAYES_00=-2.599, FAKE_REPLY_C=2.012, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUVWZr4FhVoA; Sat, 11 May 2013 11:26:01 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 76CF221F8501; Sat, 11 May 2013 11:26:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2181; q=dns/txt; s=iport; t=1368296761; x=1369506361; h=date:from:to:cc:subject:message-id:mime-version; bh=YBf1S4xVsFYs5eNZ0aT1nrFkU5a84A6+UVQmxcqa1vM=; b=Nvm/4gXqmkcNJ3qmyGlr0HO7mTtfjJ80oNl/tc+C0BT3cJqxxTmt2q46 q0oSQaB4MCe5erohwLxRL8wj1ToO/mI1wESiKEMdOq1u46rlPus7UfuVH sWQdVVagPOMFsy61SX56YR0Fb0oiPJZKmw5vfkLbnWcFOdftuIDlhmukl Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAA+NjlGrRDoI/2dsb2JhbABAEAqDBzfAIn8WdIIfAQEBBQEBNzQLGxIGCTQFEyIUE4gLDTO7LI1sgTyDXAOJGo4RAZE1gy8cPnEk
X-IronPort-AV: E=Sophos;i="4.87,653,1363132800"; d="scan'208";a="78319580"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 11 May 2013 18:25:43 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4BIPgkk030512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 May 2013 18:25:42 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r4BIPfik005361;  Sat, 11 May 2013 11:25:41 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r4BIPeGB005352; Sat, 11 May 2013 11:25:40 -0700
Date: Sat, 11 May 2013 11:25:40 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <20130511182540.GV12184@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.2i
Cc: 'Brian Haberman' <brian@innovationslab.net>, bcain99@gmail.com, ah@TR-Sys.de, holbrook@arastra.com, mboned@ietf.org, pim@ietf.org
Subject: Re: [pim] Trying to clean-up an SSM Errata Report
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 11 May 2013 18:26:05 -0000

Let me add mboned and the author of said errata.

The author of this errata seems to claim inconsistency between 4607 and
prior addressing standards (RFC3307, RFC4291). He also states: "I'm sure that
RFC 4291 should NOT be called in question.". This to me implies that he is asking
to have RFC4607 updated to remove these conflicts in RFC4607bis.

IMHO:

I have not been able to (in)validate the erratas author claims wrt. to
the interpretation of the prior RFCs. I hope others on the lists can chime
in. Assuming he is right on one or the other accounts:

I would like to see a resolution that minimizes actual deployment/interoperability
problems.

Withdrawing address ranges deemed to be useable according to existing RFC4607
in an upcoming RFC4607bis definitely has the potentialy to create mayor 
disturbances in deployments relying on those addresses. If MBoned can clearly
identify affected ranges known not to be deployed at all, then they could be
redesignated, otherwise IMHO not.

I have not seen any example of actual deployment/interoperability issues
from the incompatibility of existing RFC4607 and its claimed conflicts
with prior address architectures. It would be good if the author of the errata
(or someone else) could provide some example of such breakage.

If no real breakage could reasonably be claimed, i think RFC4607bis should
grandfather in the ranges from RFC4607 and explain how we derived at them,
and that they constitute unfortunate, but not caught violations of
principle due to the a) human nature, b) IETF process or c) the complexity
of the IPv6 address architecture. And grandfathering is not the same as
questioning RFC4291.

Cheers
    Toerless

On Sat, May 11, 2013 at 05:36:53PM +0100, Adrian Farrel wrote:
> Hi,
> 
> Take a look at http://www.rfc-editor.org/errata_search.php?eid=905
> 
> I can't make head or tail of what the appropriate resolution is. Advice please.
> 
> And any ideas if there is a better place to discuss this.
> 
> Thanks,
> Adrian
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

From bharat_joshi@infosys.com  Sun May 12 20:11:36 2013
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7842C21F846C for <pim@ietfa.amsl.com>; Sun, 12 May 2013 20:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3nA5PgdFgZUC for <pim@ietfa.amsl.com>; Sun, 12 May 2013 20:11:24 -0700 (PDT)
Received: from KECGATE08.infosys.com (kecgate08.infosysconsulting.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id C596021F89A6 for <pim@ietf.org>; Sun, 12 May 2013 20:11:23 -0700 (PDT)
X-TM-IMSS-Message-ID: <7f230bf2001179ef@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 7f230bf2001179ef ; Mon, 13 May 2013 08:47:57 +0530
Received: from BLRKECHUB06.ad.infosys.com (10.66.236.116) by blrkechub01.ad.infosys.com (10.66.236.41) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 13 May 2013 08:41:03 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by BLRKECHUB06.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Mon, 13 May 2013 08:41:03 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Stig Venaas <stig@venaas.com>, Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
Thread-Topic: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
Thread-Index: AQHOQduqGQSf6F+FGk6WsRG8zxIhsJjufku8gALHaQCAAHXTcoAG+SKAgACio7eAAiMSgIAAVj2AgAKYAwCABCJZ3Q==
Date: Mon, 13 May 2013 03:11:03 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED32E506AF@BLRKECMBX13.ad.infosys.com>
References: <20130507.112633.137013197.asaeda@sfc.wide.ad.jp> <35347FBF2796F94E936EE76C0E6047ED32E4FAAA@BLRKECMBX13.ad.infosys.com> <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp>, <518D2F0C.8030805@venaas.com>
In-Reply-To: <518D2F0C.8030805@venaas.com>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.37.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 13 May 2013 03:11:36 -0000

Hi Stig,

      Thanks for the clarification. Yes. This is what I have been trying =
to point out. It seems I was not clear enough.

Regards,
Bharat
________________________________________
From: Stig Venaas [stig@venaas.com]
Sent: Friday, May 10, 2013 11:01 PM
To: Hitoshi Asaeda
Cc: Bharat Joshi; pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking p=
im 2nd wglc

On 5/8/2013 6:55 PM, Hitoshi Asaeda wrote:
[...]
>>>>>> I tend to agree, but such protocol tuning is beyond the scope of t=
his
>>>>>> document.
>>>>>> Also, we had discussions about specific query suppression in the
>>>>>> meetings several times. Our consensus was that the specific query
>>>>>> suppression should be the option (i.e. saying "SHOULD disable this
>>>>>> specific query suppression" as you see in section 3.2).
>>
>> I agree that there is an expectation in the design of IGMP/MLD that
>> the robustness variable is set appropriately so that unsolicited
>> reports will make it through. There is always a risk that they won't
>> though. But one of the benefits of explicit tracking is "fast leave"
>> which means that you do not need to spend time on a specific query
>> before you stop forwarding. I don't think the text needs to change
>> though. It only says that this shouldn't be the default behavior. I
>> think of this as safety measure, but if you as an operator believe
>> that your link is fairly robust or that you can configure the
>> robustness count appropriately so that the chances of unsolicited
>> messages being lost is sufficiently low, then enabling specific-query
>> suppression make sense. It depends on the environment whether
>> fast-leave is important as well.
>
> I completely agree to this explanation.
> I'll add some text. Thanks.

I have one concern here. I noticed that the specific query suppression
text says:

    Specific or Group-and-Source Specific Query messages transmitted from
    a router, and reduce the number of Current-State Report messages
    transmitted from member hosts.  If a router enables the explicit
    tracking function with "specific query suppression", it suppresses
    specific query transmission and transmits specific query messages
    only when the router expects that the State-Change Report sender is
    the sole member of the channel, based on its membership state
    information (expressed in Section 3.1).

I believe it is fairly common to also suppress specific query when the
last member is leaving, in order to do "fast-leave". Basically stopping
forwarding without having to wait for responses to specific queries.

I vaguely remember we discussed this a couple of years ago...

I was thinking of this when I wrote "fast-leave" above. If you can
expect the robustness to be tuned appropriately, this should be
fairly safe. See what I wrote regarding tradeoff above.

I think Bharat was mentioning this as well, although I'm not quite sure
if I got his point.

Stig

> Regards,
> --
> Hitoshi Asaeda
>


**************** 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 stig@venaas.com  Mon May 13 10:21:13 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2BD21F9344; Mon, 13 May 2013 10:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-gV8BpbzncL; Mon, 13 May 2013 10:21:12 -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 2C7A121F931B; Mon, 13 May 2013 10:21:11 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 2D39482E2; Mon, 13 May 2013 19:21:07 +0200 (CEST)
Message-ID: <51912101.1090002@venaas.com>
Date: Mon, 13 May 2013 10:21:05 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Toerless Eckert <eckert@cisco.com>
References: <20130511182540.GV12184@cisco.com>
In-Reply-To: <20130511182540.GV12184@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'Brian Haberman' <brian@innovationslab.net>, bcain99@gmail.com, ah@TR-Sys.de, holbrook@arastra.com, mboned@ietf.org, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, pim@ietf.org
Subject: Re: [pim] Trying to clean-up an SSM Errata Report
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 13 May 2013 17:21:13 -0000

Hi

On 5/11/2013 11:25 AM, Toerless Eckert wrote:
> Let me add mboned and the author of said errata.
>
> The author of this errata seems to claim inconsistency between 4607 and
> prior addressing standards (RFC3307, RFC4291). He also states: "I'm sure that
> RFC 4291 should NOT be called in question.". This to me implies that he is asking
> to have RFC4607 updated to remove these conflicts in RFC4607bis.

Med (copied) and I are trying to get some of these issues resolved, we
have one draft (draft-ietf-6man-multicast-addr-arch-update) that will
try to clarify and resolve some conflicts. We intent to discuss some of
these SSM issues mentioned here as well. We will probably both on the
list and in the next IETF meeting try to discuss some of these issues.

We've been focusing on how the flag bits are used, and one of the cases
is the use of the transient flag and SSM.

Perhaps this thread is a good opportunity to move forward on this topic.
One question in particular, is whether the T bit should be allowed to be
0 for SSM, and whether the IANA SSM assignments (non-yet) should have
T=0.

Stig

> IMHO:
>
> I have not been able to (in)validate the erratas author claims wrt. to
> the interpretation of the prior RFCs. I hope others on the lists can chime
> in. Assuming he is right on one or the other accounts:
>
> I would like to see a resolution that minimizes actual deployment/interoperability
> problems.
>
> Withdrawing address ranges deemed to be useable according to existing RFC4607
> in an upcoming RFC4607bis definitely has the potentialy to create mayor
> disturbances in deployments relying on those addresses. If MBoned can clearly
> identify affected ranges known not to be deployed at all, then they could be
> redesignated, otherwise IMHO not.
>
> I have not seen any example of actual deployment/interoperability issues
> from the incompatibility of existing RFC4607 and its claimed conflicts
> with prior address architectures. It would be good if the author of the errata
> (or someone else) could provide some example of such breakage.
>
> If no real breakage could reasonably be claimed, i think RFC4607bis should
> grandfather in the ranges from RFC4607 and explain how we derived at them,
> and that they constitute unfortunate, but not caught violations of
> principle due to the a) human nature, b) IETF process or c) the complexity
> of the IPv6 address architecture. And grandfathering is not the same as
> questioning RFC4291.
>
> Cheers
>      Toerless
>
> On Sat, May 11, 2013 at 05:36:53PM +0100, Adrian Farrel wrote:
>> Hi,
>>
>> Take a look at http://www.rfc-editor.org/errata_search.php?eid=905
>>
>> I can't make head or tail of what the appropriate resolution is. Advice please.
>>
>> And any ideas if there is a better place to discuss this.
>>
>> Thanks,
>> Adrian
>>
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>


From asaeda@sfc.wide.ad.jp  Mon May 13 22:40:06 2013
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B5A21F8528 for <pim@ietfa.amsl.com>; Mon, 13 May 2013 22:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQVI+trcZbJH for <pim@ietfa.amsl.com>; Mon, 13 May 2013 22:40:05 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 455CF21F851C for <pim@ietf.org>; Mon, 13 May 2013 22:40:03 -0700 (PDT)
Received: from localhost (unknown [133.69.32.86]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 2DFB627807D; Tue, 14 May 2013 14:40:01 +0900 (JST)
Date: Tue, 14 May 2013 14:40:03 +0900 (JST)
Message-Id: <20130514.144003.46061186.asaeda@sfc.wide.ad.jp>
To: stig@venaas.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <518D2F0C.8030805@venaas.com>
References: <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp> <518D2F0C.8030805@venaas.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 14 May 2013 05:40:06 -0000

>    Specific or Group-and-Source Specific Query messages transmitted from
>    a router, and reduce the number of Current-State Report messages
>    transmitted from member hosts.  If a router enables the explicit
>    tracking function with "specific query suppression", it suppresses
>    specific query transmission and transmits specific query messages
>    only when the router expects that the State-Change Report sender is
>    the sole member of the channel, based on its membership state
>    information (expressed in Section 3.1).
> 
> I believe it is fairly common to also suppress specific query when the
> last member is leaving, in order to do "fast-leave". Basically
> stopping
> forwarding without having to wait for responses to specific queries.
> 
> I vaguely remember we discussed this a couple of years ago...
> 
> I was thinking of this when I wrote "fast-leave" above. If you can
> expect the robustness to be tuned appropriately, this should be
> fairly safe. See what I wrote regarding tradeoff above.

Ok, so how about the following text added at the last part of the
section titled "Lowering the Risk of Wrong Membership State"?
(Do you have any suggestion of "may", "will", etc. in this para, too?)

  In order to reduce the possibility of the incorrect membership
  expectation and keep the up-to-date membership state information,
  operators may configure the LMQC/LLQC value to 2 (the default value
  of the [Robustness Variable] value) or bigger value for their
  routers enabling the explicit tracking function with specific query
  suppression. However, if operators believe that their link is fairly
  robust or that they can configure the [Robustness Variable] value
  appropriately so that the chances of unsolicited messages being lost
  are sufficiently low, they will enable specific query suppression
  and configure both or either of the LMQC/LLQC value and the
  [Robustness Variable] value to 1 for their routers.

Regards,
--
Hitoshi Asaeda

From stig@venaas.com  Tue May 14 10:05:38 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E21721F915B for <pim@ietfa.amsl.com>; Tue, 14 May 2013 10:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDgGYsD+vn3L for <pim@ietfa.amsl.com>; Tue, 14 May 2013 10:05:25 -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 7E55721F8B64 for <pim@ietf.org>; Tue, 14 May 2013 10:05:17 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 485248285; Tue, 14 May 2013 19:05:04 +0200 (CEST)
Message-ID: <51926EB8.9090602@venaas.com>
Date: Tue, 14 May 2013 10:04:56 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
References: <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp> <518D2F0C.8030805@venaas.com> <20130514.144003.46061186.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130514.144003.46061186.asaeda@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pim@ietf.org
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 14 May 2013 17:05:40 -0000

Hi

On 5/13/2013 10:40 PM, Hitoshi Asaeda wrote:
>>     Specific or Group-and-Source Specific Query messages transmitted from
>>     a router, and reduce the number of Current-State Report messages
>>     transmitted from member hosts.  If a router enables the explicit
>>     tracking function with "specific query suppression", it suppresses
>>     specific query transmission and transmits specific query messages
>>     only when the router expects that the State-Change Report sender is
>>     the sole member of the channel, based on its membership state
>>     information (expressed in Section 3.1).
>>
>> I believe it is fairly common to also suppress specific query when the
>> last member is leaving, in order to do "fast-leave". Basically
>> stopping
>> forwarding without having to wait for responses to specific queries.
>>
>> I vaguely remember we discussed this a couple of years ago...
>>
>> I was thinking of this when I wrote "fast-leave" above. If you can
>> expect the robustness to be tuned appropriately, this should be
>> fairly safe. See what I wrote regarding tradeoff above.
>
> Ok, so how about the following text added at the last part of the
> section titled "Lowering the Risk of Wrong Membership State"?
> (Do you have any suggestion of "may", "will", etc. in this para, too?)

Is this text replacing the one above?

>    In order to reduce the possibility of the incorrect membership
>    expectation and keep the up-to-date membership state information,
>    operators may configure the LMQC/LLQC value to 2 (the default value
>    of the [Robustness Variable] value) or bigger value for their
>    routers enabling the explicit tracking function with specific query

OK so far I think, but it might be better to restructure the paragraph.

>    suppression. However, if operators believe that their link is fairly
>    robust or that they can configure the [Robustness Variable] value
>    appropriately so that the chances of unsolicited messages being lost
>    are sufficiently low, they will enable specific query suppression
>    and configure both or either of the LMQC/LLQC value and the
>    [Robustness Variable] value to 1 for their routers.

This doesn't read well. First you say they can configure the robustness
value appropriately, and at the end you say it can be set to 1.

If you don't do last member queries, then I would think you probably
want it to be default or higher. It depends though.

I think we need perhaps a paragraph by itself explaining that when
Specific Query Suppression is enabled, implementations may skip doing
a specific query when the last known member leaves. This should add
some text saying that this assumes that the robustness variable is
configured appropriately so that the risk of the router missing the
unsolicited membership reports from a host is very low. Basically that
the unsolicited reports by themselves are sufficient for the router to
keep track of all the receivers.

This text probably belongs in 3.2? In 3.3 you could then refer to 3.2
and say that one way of shortening the latency is not to do specific
queries at all when last member is leaving. If specific queries are
sent, then LMQC/LLQC etc. matters.

Stig

> Regards,
> --
> Hitoshi Asaeda
>


From bharat_joshi@infosys.com  Tue May 14 10:20:59 2013
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13EAE21F8470 for <pim@ietfa.amsl.com>; Tue, 14 May 2013 10:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94eqJDvORut4 for <pim@ietfa.amsl.com>; Tue, 14 May 2013 10:20:53 -0700 (PDT)
Received: from KECGATE03.infosys.com (kecgate03.infosysconsulting.com [122.98.10.31]) by ietfa.amsl.com (Postfix) with ESMTP id DDBED21F90FC for <pim@ietf.org>; Tue, 14 May 2013 10:20:40 -0700 (PDT)
X-TM-IMSS-Message-ID: <874de18b0004abcf@infosys.com>
Received: from BLRKECHUB05.ad.infosys.com ([10.66.236.45]) by infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service 7.1) id 874de18b0004abcf ; Tue, 14 May 2013 22:41:23 +0530
Received: from BLRKECHUB07.ad.infosys.com (10.66.236.117) by BLRKECHUB05.ad.infosys.com (10.66.236.45) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 14 May 2013 22:48:29 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by BLRKECHUB07.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Tue, 14 May 2013 22:48:29 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
Thread-Topic: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
Thread-Index: AQHOQduqGQSf6F+FGk6WsRG8zxIhsJjufku8gALHaQCAAHXTcoAG+SKAgACio7eAAiMSgIAAVj2AgAKYAwCABYJtgIABHb8b
Date: Tue, 14 May 2013 17:18:28 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED32E50BCE@BLRKECMBX13.ad.infosys.com>
References: <518AB9B1.7010601@venaas.com> <20130509.105521.204388480.asaeda@sfc.wide.ad.jp> <518D2F0C.8030805@venaas.com>, <20130514.144003.46061186.asaeda@sfc.wide.ad.jp>
In-Reply-To: <20130514.144003.46061186.asaeda@sfc.wide.ad.jp>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.37.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Please respond! Re: draft-ietf-pim-explicit-tracking pim 2nd wglc
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 14 May 2013 17:20:59 -0000

Hi Hitoshi,

         Please see in line.

Regards,
Bharat

>>    Specific or Group-and-Source Specific Query messages transmitted fr=
om
>>    a router, and reduce the number of Current-State Report messages
>>    transmitted from member hosts.  If a router enables the explicit
>>    tracking function with "specific query suppression", it suppresses
>>    specific query transmission and transmits specific query messages
>>    only when the router expects that the State-Change Report sender is
>>    the sole member of the channel, based on its membership state
>>    information (expressed in Section 3.1).
>>
>> I believe it is fairly common to also suppress specific query when the
>> last member is leaving, in order to do "fast-leave". Basically
>> stopping
>> forwarding without having to wait for responses to specific queries.
>>
>> I vaguely remember we discussed this a couple of years ago...
>>
>> I was thinking of this when I wrote "fast-leave" above. If you can
>> expect the robustness to be tuned appropriately, this should be
>> fairly safe. See what I wrote regarding tradeoff above.
>
>Ok, so how about the following text added at the last part of the
>section titled "Lowering the Risk of Wrong Membership State"?
>(Do you have any suggestion of "may", "will", etc. in this para, too?)
>
> In order to reduce the possibility of the incorrect membership
>  expectation and keep the up-to-date membership state information,
> operators may configure the LMQC/LLQC value to 2 (the default value
>  of the [Robustness Variable] value) or bigger value for their
>  routers enabling the explicit tracking function with specific query
>  suppression. However, if operators believe that their link is fairly
>  robust or that they can configure the [Robustness Variable] value
>  appropriately so that the chances of unsolicited messages being lost
>  are sufficiently low, they will enable specific query suppression
>  and configure both or either of the LMQC/LLQC value and the
>  [Robustness Variable] value to 1 for their routers.

I am looking for one things for this particular comment. 

Somewhere we need to mention that how explicit tracking function works if=
 network robustness makes sure that at least one unsolicited report messa=
ge will reach router. I think we need to add a separate section for this.=
 If you want, I can send you some text I am looking for.
**************** 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 stig@venaas.com  Tue May 21 09:56:47 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C842621F91BC for <pim@ietfa.amsl.com>; Tue, 21 May 2013 09:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shFNUXSm4Mmn for <pim@ietfa.amsl.com>; Tue, 21 May 2013 09:56:47 -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 75EF321F935E for <pim@ietf.org>; Tue, 21 May 2013 09:56:46 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 43AFA8258 for <pim@ietf.org>; Tue, 21 May 2013 18:56:44 +0200 (CEST)
Message-ID: <519BA747.1030201@venaas.com>
Date: Tue, 21 May 2013 09:56:39 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [pim] pim WGLC for draft-ietf-pim-rfc4601-update-survey-report-00
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 21 May 2013 16:56:47 -0000

Hi

We, the chairs, want to speed up the process of updating RFC 4601
and as a next step we want to make sure that you, the working group,
are happy with the implementation report. Once the group is happy, we
want to get the report published, and then finalize the updates to
4601 based on that.

The report results have been presented to the group. There were some
comments in the adoption call, and the adopted version took them into
account. The draft is available at
http://tools.ietf.org/html/draft-ietf-pim-rfc4601-update-survey-report-00

With this email we're starting a working group last call, ending
Sunday June 2nd. This is important work and we need your review. It
is the bases for updating one of our core RFCs, please read through
the report and tell us whether it is ready to be published.

Stig

From mmcbride7@gmail.com  Tue May 21 23:16:59 2013
Return-Path: <mmcbride7@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6A821F9371 for <pim@ietfa.amsl.com>; Tue, 21 May 2013 23:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.189
X-Spam-Level: 
X-Spam-Status: No, score=0.189 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQCaCcShCm1E for <pim@ietfa.amsl.com>; Tue, 21 May 2013 23:16:58 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0192E21F9399 for <pim@ietf.org>; Tue, 21 May 2013 23:16:57 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id a12so806350wgh.23 for <pim@ietf.org>; Tue, 21 May 2013 23:16:57 -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:content-transfer-encoding; bh=WAl2rcjKE+64iAmIIOixj77fab1mGHzkLYffp/oz5do=; b=vP7feuWyCqZRhdWRQFOAwSsERO0kj0SKHO99ooFb99sigkqCdPF9Nz7GIXmKqMQUEN R52/+zA1u3bbo/EjMOWCyrdLdZrg7qOa6DTZQ5VN206XDfEHXn8IPDAzrlOTqHzxqg2g xzB9ZsudG8KRluTmYB2AgCGFMN5Wdic2z7HgH+x2+tDDm0QNwgcbx16ag4I+bIrIhcM/ LHtr0BcDGuaA7UgklCFs9ElPrT7x/8Ap1GgZE1yss3XosOlMffFCZQJ2C3Y7ar9r92QE IeYgjUGSEsELhQ2qQZCM+i6GRh9WjSkyVcHchB5EF/LzRUFFGh7BdzGgJ40uqaSGxaUA vjXw==
MIME-Version: 1.0
X-Received: by 10.180.210.207 with SMTP id mw15mr11395301wic.10.1369203417062;  Tue, 21 May 2013 23:16:57 -0700 (PDT)
Received: by 10.194.222.35 with HTTP; Tue, 21 May 2013 23:16:57 -0700 (PDT)
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com>
Date: Tue, 21 May 2013 23:16:57 -0700
Message-ID: <CAL3FGfy2WdAmtnUO97nx0TYMeMqStkUmJfa42VDu=6MOykbzwQ@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, sganesan@extremenetworks.com, rajiva@cisco.com, pjhingra@cisco.com, weizho2@cisco.com
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable
Cc: Mike McBride <mmcbride7@gmail.com>, pim@ietf.org
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 22 May 2013 06:16:59 -0000

Folks,

We have this new draft-zhou-pim-vrrp-01 which we are about to adopt
into the pim wg. It has been brought to the WGs attention that there
is a older draft (draft-xu-pim-drpriority-auto-adjustment-03) which
may have some overlap with the new one. That older draft does contain
information about VRRP aware PIM which is attributed to Stig in the
acknowledgements. If the five of you authors feel that there is some
validity that the older draft contains some information being used in
the new draft, you may want to acknowledge that in the references or
acknowledgements. It appears the drafts are dissimilar enough to not
be merged but I may be wrong. Please share your opinions on this so we
can establish consensus within the group and move the document along.

If the broader WG participants have an opinion on this please speak up.

thanks,
mike

On Thu, May 9, 2013 at 7:32 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> Hi all,
>
> This draft reminds me that there has been a draft (http://tools.ietf.org/=
html/draft-xu-pim-drpriority-auto-adjustment-03) three years before which u=
ses almost the same technology to save almost the same problem.
>
> The following is quoted from the above draft:
>
>    "In fact, if VRRP is run on the PIM routers and the VRRP has enabled
>    the upstream link tracking mechanism, the PIM DR failover mechanism
>    could be coupled with the VRRP so as to reuse the upstream link
>    tracking mechanism of VRRP. One option is to synchronize the PIM DR
>    priority value to the VRRP priority value always. In this way, the
>    PIM DR and the VRRP master will always run on an identical router if
>    the VRRP Preempt_Mode is set to True. Another option is to make the
>    PIM DR and the VRRP master run on an identical router anyway (i.e.,
>    regardless whether or not the VRRP Preempt_Mode is True). To achieve
>    this goal, the PIM DR priority of the VRRP master router SHOULD
>    always be set to a higher fixed value than that of the VRRP slave
>    router automatically."
>
> Best regards,
> Xiaohu
>
>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
>> =B7=A2=BC=FE=C8=CB: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] =
=B4=FA=B1=ED Mike
>> McBride
>> =B7=A2=CB=CD=CA=B1=BC=E4: 2013=C4=EA5=D4=C210=C8=D5 3:48
>> =CA=D5=BC=FE=C8=CB: pim@ietf.org
>> =D6=F7=CC=E2: [pim] call for adoption: draft-zhou-pim-vrrp-01
>>
>> draft-zhou-pim-vrrp-01 was presented in our most recent pim meeting in
>> Orlando. 4 people were in favor of adopting the draft. Zero against.
>> Please read the draft (its short) and provide an opinion either way by
>> the end of next Friday the 17th.
>>
>> http://www.ietf.org/id/draft-zhou-pim-vrrp-01.txt
>>
>> thanks,
>> mike
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim

From rajiva@cisco.com  Wed May 22 14:36:38 2013
Return-Path: <rajiva@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2594711E8123 for <pim@ietfa.amsl.com>; Wed, 22 May 2013 14:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.328
X-Spam-Level: 
X-Spam-Status: No, score=-8.328 tagged_above=-999 required=5 tests=[AWL=-2.271, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CGe3KhFoBhV3 for <pim@ietfa.amsl.com>; Wed, 22 May 2013 14:36:33 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id DE60411E811B for <pim@ietf.org>; Wed, 22 May 2013 14:36:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4804; q=dns/txt; s=iport; t=1369258593; x=1370468193; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hVgIDs4Am+vtbCT5r0aL7pVqxXzG2Ovexe1xO9xPBRg=; b=V1gA80kvJaKVr0AxCYnt3C4IS1eUo1Ot6aBHjUZU27IWsPbzDi1uPnvP nYdw84FP7TxLjENu5tNilpVyMaabgKuB39PP6eWFRdOYe36NqiD2Rb9Lx yHqPvrHHr3FJGyn76cjZZHnnl8rur0tDacfLC/8cPIeYRSBMjrtp8WxtS Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8FADI5nVGtJV2d/2dsb2JhbABagwgwgzu+Ow16FnSCIwEBAQQBAQEaFzoLDAQCAQYCEQQBAQEEBh0FAgIfBgsUCQgCBAENBQgBh3IDDwyOBpseCIhfDYh0gSKLJIImFhsHBoI3NmEDlVKDD4p0hSODD4Im
X-IronPort-AV: E=Sophos;i="4.87,724,1363132800"; d="scan'208";a="213805441"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-2.cisco.com with ESMTP; 22 May 2013 21:36:28 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4MLaSPC017606 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 22 May 2013 21:36:28 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.154]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Wed, 22 May 2013 16:36:27 -0500
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Mike McBride <mmcbride7@gmail.com>, Xuxiaohu <xuxiaohu@huawei.com>, "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>, "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>, "Wei Zhou (weizho2)" <weizho2@cisco.com>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOVrP+ivzvTZvrmky2qTiDZ//NRpkRujug
Date: Wed, 22 May 2013 21:36:27 +0000
Message-ID: <B14A62A57AB87D45BB6DD7D9D2B78F0B116B0DB0@xmb-rcd-x06.cisco.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com> <CAL3FGfy2WdAmtnUO97nx0TYMeMqStkUmJfa42VDu=6MOykbzwQ@mail.gmail.com>
In-Reply-To: <CAL3FGfy2WdAmtnUO97nx0TYMeMqStkUmJfa42VDu=6MOykbzwQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.213.252]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 22 May 2013 21:36:38 -0000

SGkgTWlrZSwNCg0KSXQgc2VlbXMgdGhhdCBib3RoIGRyYWZ0cyBzZWVtIHRvIHNvbHZlIG5lYXJs
eSB0aGUgc2FtZSBwcm9ibGVtIChtdWx0aXBsZSByb3V0ZXJzIG9uIHRoZSBtdWx0aS1hY2Nlc3Mg
aW50ZXJmYWNlIGFuZCBleGlzdGVuY2Ugb2YgZmlyc3QtaG9wIHJlZHVuZGFuY3kgcHJvdG9jb2xz
IGUuZy4gVlJSUCkuIA0KDQpDaGVlcnMsDQpSYWppdg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogTWlrZSBNY0JyaWRlIFttYWlsdG86bW1jYnJpZGU3QGdtYWlsLmNv
bV0NCj4gU2VudDogV2VkbmVzZGF5LCBNYXkgMjIsIDIwMTMgMjoxNyBBTQ0KPiBUbzogWHV4aWFv
aHU7IHNnYW5lc2FuQGV4dHJlbWVuZXR3b3Jrcy5jb207IFJhaml2IEFzYXRpIChyYWppdmEpOw0K
PiBQcmFzaGFudCBKaGluZ3JhbiAocGpoaW5ncmEpOyBXZWkgWmhvdSAod2VpemhvMikNCj4gQ2M6
IFN0aWcgVmVuYWFzOyBNaWtlIE1jQnJpZGU7IHBpbUBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTog
W3BpbV0gY2FsbCBmb3IgYWRvcHRpb246IGRyYWZ0LXpob3UtcGltLXZycnAtMDENCj4gDQo+IEZv
bGtzLA0KPiANCj4gV2UgaGF2ZSB0aGlzIG5ldyBkcmFmdC16aG91LXBpbS12cnJwLTAxIHdoaWNo
IHdlIGFyZSBhYm91dCB0byBhZG9wdCBpbnRvDQo+IHRoZSBwaW0gd2cuIEl0IGhhcyBiZWVuIGJy
b3VnaHQgdG8gdGhlIFdHcyBhdHRlbnRpb24gdGhhdCB0aGVyZSBpcyBhIG9sZGVyDQo+IGRyYWZ0
IChkcmFmdC14dS1waW0tZHJwcmlvcml0eS1hdXRvLWFkanVzdG1lbnQtMDMpIHdoaWNoIG1heSBo
YXZlIHNvbWUNCj4gb3ZlcmxhcCB3aXRoIHRoZSBuZXcgb25lLiBUaGF0IG9sZGVyIGRyYWZ0IGRv
ZXMgY29udGFpbiBpbmZvcm1hdGlvbiBhYm91dA0KPiBWUlJQIGF3YXJlIFBJTSB3aGljaCBpcyBh
dHRyaWJ1dGVkIHRvIFN0aWcgaW4gdGhlIGFja25vd2xlZGdlbWVudHMuIElmIHRoZQ0KPiBmaXZl
IG9mIHlvdSBhdXRob3JzIGZlZWwgdGhhdCB0aGVyZSBpcyBzb21lIHZhbGlkaXR5IHRoYXQgdGhl
IG9sZGVyIGRyYWZ0DQo+IGNvbnRhaW5zIHNvbWUgaW5mb3JtYXRpb24gYmVpbmcgdXNlZCBpbiB0
aGUgbmV3IGRyYWZ0LCB5b3UgbWF5IHdhbnQgdG8NCj4gYWNrbm93bGVkZ2UgdGhhdCBpbiB0aGUg
cmVmZXJlbmNlcyBvciBhY2tub3dsZWRnZW1lbnRzLiBJdCBhcHBlYXJzIHRoZQ0KPiBkcmFmdHMg
YXJlIGRpc3NpbWlsYXIgZW5vdWdoIHRvIG5vdCBiZSBtZXJnZWQgYnV0IEkgbWF5IGJlIHdyb25n
LiBQbGVhc2UNCj4gc2hhcmUgeW91ciBvcGluaW9ucyBvbiB0aGlzIHNvIHdlIGNhbiBlc3RhYmxp
c2ggY29uc2Vuc3VzIHdpdGhpbiB0aGUgZ3JvdXANCj4gYW5kIG1vdmUgdGhlIGRvY3VtZW50IGFs
b25nLg0KPiANCj4gSWYgdGhlIGJyb2FkZXIgV0cgcGFydGljaXBhbnRzIGhhdmUgYW4gb3Bpbmlv
biBvbiB0aGlzIHBsZWFzZSBzcGVhayB1cC4NCj4gDQo+IHRoYW5rcywNCj4gbWlrZQ0KPiANCj4g
T24gVGh1LCBNYXkgOSwgMjAxMyBhdCA3OjMyIFBNLCBYdXhpYW9odSA8eHV4aWFvaHVAaHVhd2Vp
LmNvbT4gd3JvdGU6DQo+ID4gSGkgYWxsLA0KPiA+DQo+ID4gVGhpcyBkcmFmdCByZW1pbmRzIG1l
IHRoYXQgdGhlcmUgaGFzIGJlZW4gYSBkcmFmdA0KPiAoaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQteHUtcGltLWRycHJpb3JpdHktYXV0by1hZGp1c3RtZW50LTAzKQ0KPiB0aHJlZSB5
ZWFycyBiZWZvcmUgd2hpY2ggdXNlcyBhbG1vc3QgdGhlIHNhbWUgdGVjaG5vbG9neSB0byBzYXZl
IGFsbW9zdA0KPiB0aGUgc2FtZSBwcm9ibGVtLg0KPiA+DQo+ID4gVGhlIGZvbGxvd2luZyBpcyBx
dW90ZWQgZnJvbSB0aGUgYWJvdmUgZHJhZnQ6DQo+ID4NCj4gPiAgICAiSW4gZmFjdCwgaWYgVlJS
UCBpcyBydW4gb24gdGhlIFBJTSByb3V0ZXJzIGFuZCB0aGUgVlJSUCBoYXMgZW5hYmxlZA0KPiA+
ICAgIHRoZSB1cHN0cmVhbSBsaW5rIHRyYWNraW5nIG1lY2hhbmlzbSwgdGhlIFBJTSBEUiBmYWls
b3ZlciBtZWNoYW5pc20NCj4gPiAgICBjb3VsZCBiZSBjb3VwbGVkIHdpdGggdGhlIFZSUlAgc28g
YXMgdG8gcmV1c2UgdGhlIHVwc3RyZWFtIGxpbmsNCj4gPiAgICB0cmFja2luZyBtZWNoYW5pc20g
b2YgVlJSUC4gT25lIG9wdGlvbiBpcyB0byBzeW5jaHJvbml6ZSB0aGUgUElNIERSDQo+ID4gICAg
cHJpb3JpdHkgdmFsdWUgdG8gdGhlIFZSUlAgcHJpb3JpdHkgdmFsdWUgYWx3YXlzLiBJbiB0aGlz
IHdheSwgdGhlDQo+ID4gICAgUElNIERSIGFuZCB0aGUgVlJSUCBtYXN0ZXIgd2lsbCBhbHdheXMg
cnVuIG9uIGFuIGlkZW50aWNhbCByb3V0ZXIgaWYNCj4gPiAgICB0aGUgVlJSUCBQcmVlbXB0X01v
ZGUgaXMgc2V0IHRvIFRydWUuIEFub3RoZXIgb3B0aW9uIGlzIHRvIG1ha2UgdGhlDQo+ID4gICAg
UElNIERSIGFuZCB0aGUgVlJSUCBtYXN0ZXIgcnVuIG9uIGFuIGlkZW50aWNhbCByb3V0ZXIgYW55
d2F5IChpLmUuLA0KPiA+ICAgIHJlZ2FyZGxlc3Mgd2hldGhlciBvciBub3QgdGhlIFZSUlAgUHJl
ZW1wdF9Nb2RlIGlzIFRydWUpLiBUbyBhY2hpZXZlDQo+ID4gICAgdGhpcyBnb2FsLCB0aGUgUElN
IERSIHByaW9yaXR5IG9mIHRoZSBWUlJQIG1hc3RlciByb3V0ZXIgU0hPVUxEDQo+ID4gICAgYWx3
YXlzIGJlIHNldCB0byBhIGhpZ2hlciBmaXhlZCB2YWx1ZSB0aGFuIHRoYXQgb2YgdGhlIFZSUlAg
c2xhdmUNCj4gPiAgICByb3V0ZXIgYXV0b21hdGljYWxseS4iDQo+ID4NCj4gPiBCZXN0IHJlZ2Fy
ZHMsDQo+ID4gWGlhb2h1DQo+ID4NCj4gPj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ID4+ILeivP7I
yzogcGltLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpwaW0tYm91bmNlc0BpZXRmLm9yZ10gtPqx
7Q0KPiBNaWtlDQo+ID4+IE1jQnJpZGUNCj4gPj4gt6LLzcqxvOQ6IDIwMTPE6jXUwjEwyNUgMzo0
OA0KPiA+PiDK1bz+yMs6IHBpbUBpZXRmLm9yZw0KPiA+PiDW98ziOiBbcGltXSBjYWxsIGZvciBh
ZG9wdGlvbjogZHJhZnQtemhvdS1waW0tdnJycC0wMQ0KPiA+Pg0KPiA+PiBkcmFmdC16aG91LXBp
bS12cnJwLTAxIHdhcyBwcmVzZW50ZWQgaW4gb3VyIG1vc3QgcmVjZW50IHBpbSBtZWV0aW5nDQo+
ID4+IGluIE9ybGFuZG8uIDQgcGVvcGxlIHdlcmUgaW4gZmF2b3Igb2YgYWRvcHRpbmcgdGhlIGRy
YWZ0LiBaZXJvIGFnYWluc3QuDQo+ID4+IFBsZWFzZSByZWFkIHRoZSBkcmFmdCAoaXRzIHNob3J0
KSBhbmQgcHJvdmlkZSBhbiBvcGluaW9uIGVpdGhlciB3YXkNCj4gPj4gYnkgdGhlIGVuZCBvZiBu
ZXh0IEZyaWRheSB0aGUgMTd0aC4NCj4gPj4NCj4gPj4gaHR0cDovL3d3dy5pZXRmLm9yZy9pZC9k
cmFmdC16aG91LXBpbS12cnJwLTAxLnR4dA0KPiA+Pg0KPiA+PiB0aGFua3MsDQo+ID4+IG1pa2UN
Cj4gPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4g
Pj4gcGltIG1haWxpbmcgbGlzdA0KPiA+PiBwaW1AaWV0Zi5vcmcNCj4gPj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW0NCg==

From william.atwood@concordia.ca  Wed May 22 20:28:13 2013
Return-Path: <william.atwood@concordia.ca>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738A811E8164 for <pim@ietfa.amsl.com>; Wed, 22 May 2013 20:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EqxOES0j+zsX for <pim@ietfa.amsl.com>; Wed, 22 May 2013 20:28:09 -0700 (PDT)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.92]) by ietfa.amsl.com (Postfix) with ESMTP id 175E211E812C for <pim@ietf.org>; Wed, 22 May 2013 20:28:07 -0700 (PDT)
Received: from [127.0.0.1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id r4N3S5Ys028848 for <pim@ietf.org>; Wed, 22 May 2013 23:28:05 -0400
Message-ID: <519D8CCC.9010907@concordia.ca>
Date: Wed, 22 May 2013 23:28:12 -0400
From: William Atwood <william.atwood@concordia.ca>
Organization: Concordia University, Montreal
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: pim@ietf.org
References: <519BA747.1030201@venaas.com>
In-Reply-To: <519BA747.1030201@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2013/05/22 23:28:05 EDT
Subject: Re: [pim] pim WGLC for draft-ietf-pim-rfc4601-update-survey-report-00
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 23 May 2013 03:28:13 -0000

Hello,

I am happy with the report, with the exception of some grammatical
issues that I have sent to the authors off-list.

Once these are corrected, I believe that the draft will be ready to publish.

  Bill

On 21/05/2013 12:56 PM, Stig Venaas wrote:
> Hi
> 
> We, the chairs, want to speed up the process of updating RFC 4601
> and as a next step we want to make sure that you, the working group,
> are happy with the implementation report. Once the group is happy, we
> want to get the report published, and then finalize the updates to
> 4601 based on that.
> 
> The report results have been presented to the group. There were some
> comments in the adoption call, and the adopted version took them into
> account. The draft is available at
> http://tools.ietf.org/html/draft-ietf-pim-rfc4601-update-survey-report-00
> 
> With this email we're starting a working group last call, ending
> Sunday June 2nd. This is important work and we need your review. It
> is the bases for updating one of our core RFCs, please read through
> the report and tell us whether it is ready to be published.
> 
> Stig
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

-- 
Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email:william.atwood@concordia.ca
1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8

From pjhingra@cisco.com  Thu May 23 02:08:39 2013
Return-Path: <pjhingra@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC7E21F9702 for <pim@ietfa.amsl.com>; Thu, 23 May 2013 02:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.057
X-Spam-Level: 
X-Spam-Status: No, score=-106.057 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sOL47FBVUVlB for <pim@ietfa.amsl.com>; Thu, 23 May 2013 02:08:33 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id A72B621F964C for <pim@ietf.org>; Thu, 23 May 2013 02:08:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5604; q=dns/txt; s=iport; t=1369300113; x=1370509713; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Ocaq2b4Bl3xiGIKcoqjCEpvxi/DaZHsFJi5YK9ooXOM=; b=Ulnv7tm0RVamPg0lCFNJbHFduDfz0KG2IxxlIIjzFRkPlLjRXFIgi0XX 8XFcx7Zjh9tFxo7GJTxl4a234XeUxAoYt0qDa4oKG2LGIp2CVxnvDbdpI ice3M2AXr/H0OX9ose0rO9YKWLSI5Qeha0bThWvxr67/NL0kUf2S0U80g M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au0FAJnbnVGtJXG+/2dsb2JhbABagwgwgzu+cA19FnSCIwEBAQQBAQEaFzoLDAQCAQYCEQQBAQEEBh0FAgIfBgsUCQgCBAENBQgBh3IDDwyNQZseCIhpDYh0gSKLJIImDwcbBwaCNzZhA5VSgw+KdIUjgw+CJg
X-IronPort-AV: E=Sophos;i="4.87,726,1363132800"; d="scan'208";a="213813431"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 23 May 2013 09:08:33 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4N98WHx029503 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 May 2013 09:08:32 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.194]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Thu, 23 May 2013 04:08:32 -0500
From: "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>, Mike McBride <mmcbride7@gmail.com>, Xuxiaohu <xuxiaohu@huawei.com>, "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>, "Wei Zhou (weizho2)" <weizho2@cisco.com>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOVrP+ivzvTZvrmky2qTiDZ//NRpkRujuggADBIUA=
Date: Thu, 23 May 2013 09:08:31 +0000
Message-ID: <F567B77E0728694BB6716DB3C9000B6B12ABC487@xmb-rcd-x14.cisco.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com> <CAL3FGfy2WdAmtnUO97nx0TYMeMqStkUmJfa42VDu=6MOykbzwQ@mail.gmail.com> <B14A62A57AB87D45BB6DD7D9D2B78F0B116B0DB0@xmb-rcd-x06.cisco.com>
In-Reply-To: <B14A62A57AB87D45BB6DD7D9D2B78F0B116B0DB0@xmb-rcd-x06.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.142.105.208]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 23 May 2013 09:08:39 -0000

SGkgTWlrZSwNCg0KSSBhZ3JlZSB3aXRoIFJhaml2LCBib3RoIGRyYWZ0cyBhcmUgdHJ5aW5nIHRv
IHNvbHZlIHRoZSBzYW1lIGlzc3VlLi4uLnRoYXQgdG9vIGluIGFsbW9zdCBzaW1pbGFyIHdheS4N
Cg0KLQ0KUmVnYXJkcywNClByYXNoYW50IEpoaW5ncmFuDQpOT1NURyBUTUUgLSBTUCBXaS1GaQ0K
DQpodHRwOi8vd3d3aW4uY2lzY28uY29tL2lvcy90ZWNoL21vYmlsZS9wcm94eWlwdjYvIA0KaHR0
cDovL3d3d2luLmNpc2NvLmNvbS9pb3MvdGVjaC9icm9hZGJhbmQNCg0KDQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KRnJvbTogUmFqaXYgQXNhdGkgKHJhaml2YSkgDQpTZW50OiBUaHVyc2Rh
eSwgTWF5IDIzLCAyMDEzIDM6MDYgQU0NClRvOiBNaWtlIE1jQnJpZGU7IFh1eGlhb2h1OyBzZ2Fu
ZXNhbkBleHRyZW1lbmV0d29ya3MuY29tOyBQcmFzaGFudCBKaGluZ3JhbiAocGpoaW5ncmEpOyBX
ZWkgWmhvdSAod2VpemhvMikNCkNjOiBTdGlnIFZlbmFhczsgcGltQGlldGYub3JnDQpTdWJqZWN0
OiBSRTogW3BpbV0gY2FsbCBmb3IgYWRvcHRpb246IGRyYWZ0LXpob3UtcGltLXZycnAtMDENCg0K
SGkgTWlrZSwNCg0KSXQgc2VlbXMgdGhhdCBib3RoIGRyYWZ0cyBzZWVtIHRvIHNvbHZlIG5lYXJs
eSB0aGUgc2FtZSBwcm9ibGVtIChtdWx0aXBsZSByb3V0ZXJzIG9uIHRoZSBtdWx0aS1hY2Nlc3Mg
aW50ZXJmYWNlIGFuZCBleGlzdGVuY2Ugb2YgZmlyc3QtaG9wIHJlZHVuZGFuY3kgcHJvdG9jb2xz
IGUuZy4gVlJSUCkuIA0KDQpDaGVlcnMsDQpSYWppdg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogTWlrZSBNY0JyaWRlIFttYWlsdG86bW1jYnJpZGU3QGdtYWlsLmNv
bV0NCj4gU2VudDogV2VkbmVzZGF5LCBNYXkgMjIsIDIwMTMgMjoxNyBBTQ0KPiBUbzogWHV4aWFv
aHU7IHNnYW5lc2FuQGV4dHJlbWVuZXR3b3Jrcy5jb207IFJhaml2IEFzYXRpIChyYWppdmEpOyAN
Cj4gUHJhc2hhbnQgSmhpbmdyYW4gKHBqaGluZ3JhKTsgV2VpIFpob3UgKHdlaXpobzIpDQo+IENj
OiBTdGlnIFZlbmFhczsgTWlrZSBNY0JyaWRlOyBwaW1AaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6
IFtwaW1dIGNhbGwgZm9yIGFkb3B0aW9uOiBkcmFmdC16aG91LXBpbS12cnJwLTAxDQo+IA0KPiBG
b2xrcywNCj4gDQo+IFdlIGhhdmUgdGhpcyBuZXcgZHJhZnQtemhvdS1waW0tdnJycC0wMSB3aGlj
aCB3ZSBhcmUgYWJvdXQgdG8gYWRvcHQgDQo+IGludG8gdGhlIHBpbSB3Zy4gSXQgaGFzIGJlZW4g
YnJvdWdodCB0byB0aGUgV0dzIGF0dGVudGlvbiB0aGF0IHRoZXJlIA0KPiBpcyBhIG9sZGVyIGRy
YWZ0IChkcmFmdC14dS1waW0tZHJwcmlvcml0eS1hdXRvLWFkanVzdG1lbnQtMDMpIHdoaWNoIA0K
PiBtYXkgaGF2ZSBzb21lIG92ZXJsYXAgd2l0aCB0aGUgbmV3IG9uZS4gVGhhdCBvbGRlciBkcmFm
dCBkb2VzIGNvbnRhaW4gDQo+IGluZm9ybWF0aW9uIGFib3V0IFZSUlAgYXdhcmUgUElNIHdoaWNo
IGlzIGF0dHJpYnV0ZWQgdG8gU3RpZyBpbiB0aGUgDQo+IGFja25vd2xlZGdlbWVudHMuIElmIHRo
ZSBmaXZlIG9mIHlvdSBhdXRob3JzIGZlZWwgdGhhdCB0aGVyZSBpcyBzb21lIA0KPiB2YWxpZGl0
eSB0aGF0IHRoZSBvbGRlciBkcmFmdCBjb250YWlucyBzb21lIGluZm9ybWF0aW9uIGJlaW5nIHVz
ZWQgaW4gDQo+IHRoZSBuZXcgZHJhZnQsIHlvdSBtYXkgd2FudCB0byBhY2tub3dsZWRnZSB0aGF0
IGluIHRoZSByZWZlcmVuY2VzIG9yIA0KPiBhY2tub3dsZWRnZW1lbnRzLiBJdCBhcHBlYXJzIHRo
ZSBkcmFmdHMgYXJlIGRpc3NpbWlsYXIgZW5vdWdoIHRvIG5vdCANCj4gYmUgbWVyZ2VkIGJ1dCBJ
IG1heSBiZSB3cm9uZy4gUGxlYXNlIHNoYXJlIHlvdXIgb3BpbmlvbnMgb24gdGhpcyBzbyB3ZSAN
Cj4gY2FuIGVzdGFibGlzaCBjb25zZW5zdXMgd2l0aGluIHRoZSBncm91cCBhbmQgbW92ZSB0aGUg
ZG9jdW1lbnQgYWxvbmcuDQo+IA0KPiBJZiB0aGUgYnJvYWRlciBXRyBwYXJ0aWNpcGFudHMgaGF2
ZSBhbiBvcGluaW9uIG9uIHRoaXMgcGxlYXNlIHNwZWFrIHVwLg0KPiANCj4gdGhhbmtzLA0KPiBt
aWtlDQo+IA0KPiBPbiBUaHUsIE1heSA5LCAyMDEzIGF0IDc6MzIgUE0sIFh1eGlhb2h1IDx4dXhp
YW9odUBodWF3ZWkuY29tPiB3cm90ZToNCj4gPiBIaSBhbGwsDQo+ID4NCj4gPiBUaGlzIGRyYWZ0
IHJlbWluZHMgbWUgdGhhdCB0aGVyZSBoYXMgYmVlbiBhIGRyYWZ0DQo+IChodHRwOi8vdG9vbHMu
aWV0Zi5vcmcvaHRtbC9kcmFmdC14dS1waW0tZHJwcmlvcml0eS1hdXRvLWFkanVzdG1lbnQtMDMN
Cj4gKSB0aHJlZSB5ZWFycyBiZWZvcmUgd2hpY2ggdXNlcyBhbG1vc3QgdGhlIHNhbWUgdGVjaG5v
bG9neSB0byBzYXZlIA0KPiBhbG1vc3QgdGhlIHNhbWUgcHJvYmxlbS4NCj4gPg0KPiA+IFRoZSBm
b2xsb3dpbmcgaXMgcXVvdGVkIGZyb20gdGhlIGFib3ZlIGRyYWZ0Og0KPiA+DQo+ID4gICAgIklu
IGZhY3QsIGlmIFZSUlAgaXMgcnVuIG9uIHRoZSBQSU0gcm91dGVycyBhbmQgdGhlIFZSUlAgaGFz
IGVuYWJsZWQNCj4gPiAgICB0aGUgdXBzdHJlYW0gbGluayB0cmFja2luZyBtZWNoYW5pc20sIHRo
ZSBQSU0gRFIgZmFpbG92ZXIgbWVjaGFuaXNtDQo+ID4gICAgY291bGQgYmUgY291cGxlZCB3aXRo
IHRoZSBWUlJQIHNvIGFzIHRvIHJldXNlIHRoZSB1cHN0cmVhbSBsaW5rDQo+ID4gICAgdHJhY2tp
bmcgbWVjaGFuaXNtIG9mIFZSUlAuIE9uZSBvcHRpb24gaXMgdG8gc3luY2hyb25pemUgdGhlIFBJ
TSBEUg0KPiA+ICAgIHByaW9yaXR5IHZhbHVlIHRvIHRoZSBWUlJQIHByaW9yaXR5IHZhbHVlIGFs
d2F5cy4gSW4gdGhpcyB3YXksIHRoZQ0KPiA+ICAgIFBJTSBEUiBhbmQgdGhlIFZSUlAgbWFzdGVy
IHdpbGwgYWx3YXlzIHJ1biBvbiBhbiBpZGVudGljYWwgcm91dGVyIGlmDQo+ID4gICAgdGhlIFZS
UlAgUHJlZW1wdF9Nb2RlIGlzIHNldCB0byBUcnVlLiBBbm90aGVyIG9wdGlvbiBpcyB0byBtYWtl
IHRoZQ0KPiA+ICAgIFBJTSBEUiBhbmQgdGhlIFZSUlAgbWFzdGVyIHJ1biBvbiBhbiBpZGVudGlj
YWwgcm91dGVyIGFueXdheSAoaS5lLiwNCj4gPiAgICByZWdhcmRsZXNzIHdoZXRoZXIgb3Igbm90
IHRoZSBWUlJQIFByZWVtcHRfTW9kZSBpcyBUcnVlKS4gVG8gYWNoaWV2ZQ0KPiA+ICAgIHRoaXMg
Z29hbCwgdGhlIFBJTSBEUiBwcmlvcml0eSBvZiB0aGUgVlJSUCBtYXN0ZXIgcm91dGVyIFNIT1VM
RA0KPiA+ICAgIGFsd2F5cyBiZSBzZXQgdG8gYSBoaWdoZXIgZml4ZWQgdmFsdWUgdGhhbiB0aGF0
IG9mIHRoZSBWUlJQIHNsYXZlDQo+ID4gICAgcm91dGVyIGF1dG9tYXRpY2FsbHkuIg0KPiA+DQo+
ID4gQmVzdCByZWdhcmRzLA0KPiA+IFhpYW9odQ0KPiA+DQo+ID4+IC0tLS0t08q8/tStvP4tLS0t
LQ0KPiA+PiC3orz+yMs6IHBpbS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86cGltLWJvdW5jZXNA
aWV0Zi5vcmddILT6se0NCj4gTWlrZQ0KPiA+PiBNY0JyaWRlDQo+ID4+ILeiy83KsbzkOiAyMDEz
xOo11MIxMMjVIDM6NDgNCj4gPj4gytW8/sjLOiBwaW1AaWV0Zi5vcmcNCj4gPj4g1vfM4jogW3Bp
bV0gY2FsbCBmb3IgYWRvcHRpb246IGRyYWZ0LXpob3UtcGltLXZycnAtMDENCj4gPj4NCj4gPj4g
ZHJhZnQtemhvdS1waW0tdnJycC0wMSB3YXMgcHJlc2VudGVkIGluIG91ciBtb3N0IHJlY2VudCBw
aW0gbWVldGluZyANCj4gPj4gaW4gT3JsYW5kby4gNCBwZW9wbGUgd2VyZSBpbiBmYXZvciBvZiBh
ZG9wdGluZyB0aGUgZHJhZnQuIFplcm8gYWdhaW5zdC4NCj4gPj4gUGxlYXNlIHJlYWQgdGhlIGRy
YWZ0IChpdHMgc2hvcnQpIGFuZCBwcm92aWRlIGFuIG9waW5pb24gZWl0aGVyIHdheSANCj4gPj4g
YnkgdGhlIGVuZCBvZiBuZXh0IEZyaWRheSB0aGUgMTd0aC4NCj4gPj4NCj4gPj4gaHR0cDovL3d3
dy5pZXRmLm9yZy9pZC9kcmFmdC16aG91LXBpbS12cnJwLTAxLnR4dA0KPiA+Pg0KPiA+PiB0aGFu
a3MsDQo+ID4+IG1pa2UNCj4gPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4gPj4gcGltIG1haWxpbmcgbGlzdA0KPiA+PiBwaW1AaWV0Zi5vcmcNCj4g
Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9waW0NCg==

From internet-drafts@ietf.org  Thu May 23 08:28:49 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58BD811E8170; Thu, 23 May 2013 08:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1HIY94ENLnjA; Thu, 23 May 2013 08:28:48 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DCB2F11E8143; Thu, 23 May 2013 08:28:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130523152848.21931.66216.idtracker@ietfa.amsl.com>
Date: Thu, 23 May 2013 08:28:48 -0700
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-rfc4601-update-survey-report-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 23 May 2013 15:28:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Protocol Independent Multicast Working Gr=
oup of the IETF.

	Title           : Survey Report on PIM-SM Implementations and Deployments
	Author(s)       : Lianshu Zheng
                          Zhaohui Zhang
                          Rishabh Parekh
	Filename        : draft-ietf-pim-rfc4601-update-survey-report-01.txt
	Pages           : 15
	Date            : 2013-05-23

Abstract:
   This document provides supporting documentation to advance the
   Protocol Independent Multicast - Sparse Mode (PIM-SM)
   protocol from IETF Proposed Standard to Internet Standard.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-rfc4601-update-survey-report

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pim-rfc4601-update-survey-report-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-rfc4601-update-survey-rep=
ort-01


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


From zzhang@juniper.net  Thu May 23 08:33:49 2013
Return-Path: <zzhang@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9A8C21F96B4 for <pim@ietfa.amsl.com>; Thu, 23 May 2013 08:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level: 
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7tZc9v3DPiQ3 for <pim@ietfa.amsl.com>; Thu, 23 May 2013 08:33:44 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 79B3621F96A6 for <pim@ietf.org>; Thu, 23 May 2013 08:33:44 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUZ422JorP76s0khwSCQh9rFL2/T2yacl@postini.com; Thu, 23 May 2013 08:33:44 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 23 May 2013 08:31:20 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Thu, 23 May 2013 08:31:20 -0700
Received: from am1outboundpool.messaging.microsoft.com (213.199.154.204) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 23 May 2013 08:42:01 -0700
Received: from mail88-am1-R.bigfish.com (10.3.201.230) by AM1EHSOBE020.bigfish.com (10.3.207.142) with Microsoft SMTP Server id 14.1.225.23; Thu, 23 May 2013 15:31:12 +0000
Received: from mail88-am1 (localhost [127.0.0.1])	by mail88-am1-R.bigfish.com (Postfix) with ESMTP id 6205C80441	for <pim@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 23 May 2013 15:31:12 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.101; KIP:(null); UIP:(null); (null); H:BY2PRD0510HT005.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -31
X-BigFish: PS-31(zzbb2dI98dI9371I542I1432I11f6Nzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz31h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1155h)
Received-SPF: softfail (mail88-am1: transitioning domain of juniper.net does not designate 157.56.236.101 as permitted sender) client-ip=157.56.236.101; envelope-from=zzhang@juniper.net; helo=BY2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail88-am1 (localhost.localdomain [127.0.0.1]) by mail88-am1 (MessageSwitch) id 1369323070466410_18684; Thu, 23 May 2013 15:31:10 +0000 (UTC)
Received: from AM1EHSMHS003.bigfish.com (unknown [10.3.201.235])	by mail88-am1.bigfish.com (Postfix) with ESMTP id 6526B48012D; Thu, 23 May 2013 15:31:10 +0000 (UTC)
Received: from BY2PRD0510HT005.namprd05.prod.outlook.com (157.56.236.101) by AM1EHSMHS003.bigfish.com (10.3.207.103) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 23 May 2013 15:31:08 +0000
Received: from BY2PRD0510MB389.namprd05.prod.outlook.com ([169.254.4.42]) by BY2PRD0510HT005.namprd05.prod.outlook.com ([10.255.84.40]) with mapi id 14.16.0311.000; Thu, 23 May 2013 15:31:01 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: William Atwood <william.atwood@concordia.ca>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] pim WGLC for draft-ietf-pim-rfc4601-update-survey-report-00
Thread-Index: AQHOV2WXfgcjFLJY4UeP/G5Wv0/yq5kS5dpw
Date: Thu, 23 May 2013 15:31:00 +0000
Message-ID: <0BF0FCC78340F147BE76A6F5762318A832A0E895@BY2PRD0510MB389.namprd05.prod.outlook.com>
References: <519BA747.1030201@venaas.com> <519D8CCC.9010907@concordia.ca>
In-Reply-To: <519D8CCC.9010907@concordia.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%CONCORDIA.CA$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Subject: Re: [pim] pim WGLC for	draft-ietf-pim-rfc4601-update-survey-report-00
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 23 May 2013 15:33:50 -0000

Bill,

Thank you very much for your detailed review and catching those issues. I'v=
e fixed them and posted -01 version:

URL:             http://www.ietf.org/internet-drafts/draft-ietf-pim-rfc4601=
-update-survey-report-01.txt
Status:          http://datatracker.ietf.org/doc/draft-ietf-pim-rfc4601-upd=
ate-survey-report
Htmlized:        http://tools.ietf.org/html/draft-ietf-pim-rfc4601-update-s=
urvey-report-01
Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-rfc4601-=
update-survey-report-01
=20
Jeffrey

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of
> William Atwood
> Sent: Wednesday, May 22, 2013 11:28 PM
> To: pim@ietf.org
> Subject: Re: [pim] pim WGLC for draft-ietf-pim-rfc4601-update-survey-
> report-00
>=20
> Hello,
>=20
> I am happy with the report, with the exception of some grammatical
> issues that I have sent to the authors off-list.
>=20
> Once these are corrected, I believe that the draft will be ready to
> publish.
>=20
>   Bill
>=20
> On 21/05/2013 12:56 PM, Stig Venaas wrote:
> > Hi
> >
> > We, the chairs, want to speed up the process of updating RFC 4601
> > and as a next step we want to make sure that you, the working group,
> > are happy with the implementation report. Once the group is happy, we
> > want to get the report published, and then finalize the updates to
> > 4601 based on that.
> >
> > The report results have been presented to the group. There were some
> > comments in the adoption call, and the adopted version took them into
> > account. The draft is available at
> > http://tools.ietf.org/html/draft-ietf-pim-rfc4601-update-survey-
> report-00
> >
> > With this email we're starting a working group last call, ending
> > Sunday June 2nd. This is important work and we need your review. It
> > is the bases for updating one of our core RFCs, please read through
> > the report and tell us whether it is ready to be published.
> >
> > Stig
> > _______________________________________________
> > pim mailing list
> > pim@ietf.org
> > https://www.ietf.org/mailman/listinfo/pim
>=20
> --
> Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
> Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
> Department of Computer Science
>    and Software Engineering
> Concordia University EV 3.185     email:william.atwood@concordia.ca
> 1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
> Montreal, Quebec Canada H3G 1M8
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim



From xuxiaohu@huawei.com  Thu May 23 18:56:36 2013
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F0921F9330 for <pim@ietfa.amsl.com>; Thu, 23 May 2013 18:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.057
X-Spam-Level: 
X-Spam-Status: No, score=-2.057 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDA1lNdVsDWC for <pim@ietfa.amsl.com>; Thu, 23 May 2013 18:56:31 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1153921F8FBE for <pim@ietf.org>; Thu, 23 May 2013 18:56:29 -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.5-GA FastPath queued) with ESMTP id ARR34878; Fri, 24 May 2013 01:56:29 +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.1.323.7; Fri, 24 May 2013 02:56:13 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 24 May 2013 02:56:27 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.134]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Fri, 24 May 2013 09:56:21 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Wei Zhou (weizho2)" <weizho2@cisco.com>, "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>, "Rajiv Asati (rajiva)" <rajiva@cisco.com>, Mike McBride <mmcbride7@gmail.com>, "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOVrP2yBNO9pOfGUaQq5QJP/JnZZkRNU+AgADBXYCAAND0gIAAyGuA
Date: Fri, 24 May 2013 01:56:20 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081C2A89@NKGEML512-MBS.china.huawei.com>
References: <F567B77E0728694BB6716DB3C9000B6B12ABC487@xmb-rcd-x14.cisco.com> <23EF39780ADBDE42806FAEE7B8578690183E4D44@xmb-rcd-x05.cisco.com>
In-Reply-To: <23EF39780ADBDE42806FAEE7B8578690183E4D44@xmb-rcd-x05.cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 24 May 2013 01:56:36 -0000

SGksDQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogV2VpIFpob3UgKHdlaXpobzIp
IFttYWlsdG86d2VpemhvMkBjaXNjby5jb21dDQo+ILeiy83KsbzkOiAyMDEzxOo11MIyNMjVIDU6
MzYNCj4gytW8/sjLOiBQcmFzaGFudCBKaGluZ3JhbiAocGpoaW5ncmEpOyBSYWppdiBBc2F0aSAo
cmFqaXZhKTsgTWlrZSBNY0JyaWRlOw0KPiBYdXhpYW9odTsgc2dhbmVzYW5AZXh0cmVtZW5ldHdv
cmtzLmNvbQ0KPiCzrcvNOiBTdGlnIFZlbmFhczsgcGltQGlldGYub3JnDQo+INb3zOI6IFJlOiBb
cGltXSBjYWxsIGZvciBhZG9wdGlvbjogZHJhZnQtemhvdS1waW0tdnJycC0wMQ0KPiANCj4gSGks
DQo+IA0KPiBUaGFuayB5b3UgYWxsIGZvciBwcm92aWRpbmcgY29tbWVudHMgYW5kIHRoZSBpbmZv
cm1hdGlvbiBvbg0KPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14dS1waW0tZHJw
cmlvcml0eS1hdXRvLWFkanVzdG1lbnQtMDMuDQo+IA0KPiBJIGp1c3QgcmVhZCB0aHJvdWdoIHRo
ZSBkcmFmdCBwcm9wb3NlZCBieSB4aWFvaHUgYXMgSSB3YXMgbm90IGF3YXJlIG9mDQo+IHRoaXMg
ZHJhZnQgdW50aWwgeGlhb2h1IGtpbmRseSBtZW50aW9uZWQgaW4gdGhlIG1haWwgbGlzdC4gQWZ0
ZXIgY2FyZWZ1bGx5DQo+IGNvbXBhcmluZyB0aGUgdHdvIGRyYWZ0cywgbGV0IG1lIHRyeSBleHBs
YWluIHRoZSBkaWZmZXJlbmNlcyBiZXR3ZWVuIHRoZW0NCj4gKHJlZmVycmVkIGFzIGRyYWZ0LXh1
LWRyLWFkaiBhbmQgZHJhZnQtemhvdS1waW0tdnJycCk6DQo+IA0KPiAxLiBUaGUgb3JpZ2luYWwg
cHJvYmxlbXMgdGhhdCB0d28gZHJhZnRzIHRyeSB0byBzb2x2ZSBtaWdodCBsb29rIHNpbWlsYXIN
Cj4gYnV0IHRoZXkgYXJlIGFjdHVhbGx5IHF1aXRlIGRpZmZlcmVudCBpbiB0aGUgZm9sbG93aW5n
IHdheToNCj4gZHJhZnQteHUtZHItYWRqIHRhcmdldHMgdGhlIFBJTSBEUiBhdXRvLWFkanVzdG1l
bnQgYmFzZWQgb24gdXBzdHJlYW0gbGluaw0KPiB0cmFja2luZywgd2hpbGUgdGhlIGlkZWEgaW4g
ZHJhZnQtemhvdS1waW0tdnJycCBpcyB0byBwcm92aWRlIGEgY29tcGxldGUNCj4gc29sdXRpb24g
dG8gZW5hYmxlIG11bHRpY2FzdCB0byBpbnRlcm9wZXJhdGUgd2l0aCBmaXJzdCBob3AgcmVkdW5k
YW5jeQ0KPiBwcm90b2NvbCBpbiByZXNwb25zZSB0byBhbnkgaW50ZXJlc3RlZCBldmVudHM6IE1h
c3RlciByb3V0ZXJzIGdvZXMgZG93biwNCj4gdXBzdHJlYW0gbGluayB1cC9kb3duLCBiYW5kd2lk
dGggY2hhbmdlIGFuZCBvdGhlciBsb2dpY2FsIG9iamVjdHMgdGhhdA0KPiBWUlJQIGNvdWxkIHRy
YWNrLg0KDQpBcyBpdCBzYWlkIGluIHNlY3Rpb24gMiBvZiBkcmFmdC14dS1kci1hZGosDQoNCiIg
IEluIGZhY3QsIGlmIFZSUlAgaXMgcnVuIG9uIHRoZSBQSU0gcm91dGVycyBhbmQgdGhlIFZSUlAg
aGFzIGVuYWJsZWQNCiAgIHRoZSB1cHN0cmVhbSBsaW5rIHRyYWNraW5nIG1lY2hhbmlzbSwgdGhl
IFBJTSBEUiBmYWlsb3ZlciBtZWNoYW5pc20NCiAgIGNvdWxkIGJlIGNvdXBsZWQgd2l0aCB0aGUg
VlJSUCBzbyBhcyB0byByZXVzZSB0aGUgdXBzdHJlYW0gbGluaw0KICAgdHJhY2tpbmcgbWVjaGFu
aXNtIG9mIFZSUlAuIE9uZSBvcHRpb24gaXMgdG8gc3luY2hyb25pemUgdGhlIFBJTSBEUg0KICAg
cHJpb3JpdHkgdmFsdWUgdG8gdGhlIFZSUlAgcHJpb3JpdHkgdmFsdWUgYWx3YXlzLiBJbiB0aGlz
IHdheSwgdGhlDQogICBQSU0gRFIgYW5kIHRoZSBWUlJQIG1hc3RlciB3aWxsIGFsd2F5cyBydW4g
b24gYW4gaWRlbnRpY2FsIHJvdXRlciBpZg0KICAgdGhlIFZSUlAgUHJlZW1wdF9Nb2RlIGlzIHNl
dCB0byBUcnVlLiBBbm90aGVyIG9wdGlvbiBpcyB0byBtYWtlIHRoZQ0KICAgUElNIERSIGFuZCB0
aGUgVlJSUCBtYXN0ZXIgcnVuIG9uIGFuIGlkZW50aWNhbCByb3V0ZXIgYW55d2F5IChpLmUuLA0K
ICAgcmVnYXJkbGVzcyB3aGV0aGVyIG9yIG5vdCB0aGUgVlJSUCBQcmVlbXB0X01vZGUgaXMgVHJ1
ZSkuIFRvIGFjaGlldmUNCiAgIHRoaXMgZ29hbCwgdGhlIFBJTSBEUiBwcmlvcml0eSBvZiB0aGUg
VlJSUCBtYXN0ZXIgcm91dGVyIFNIT1VMRA0KICAgYWx3YXlzIGJlIHNldCB0byBhIGhpZ2hlciBm
aXhlZCB2YWx1ZSB0aGFuIHRoYXQgb2YgdGhlIFZSUlAgc2xhdmUNCiAgIHJvdXRlciBhdXRvbWF0
aWNhbGx5Lg0KIg0KSW4gYSB3b3JkLCB0aGUgUElNIERSIGFuZCB0aGUgVlJSUCBtYXN0ZXIgY291
bGQgYWN0dWFsbHkgcnVuIG9uIHRoZSBzYW1lIHJvdXRlciBubyBtYXR0ZXIgd2hhdGV2ZXIgZmFj
dG9yIHRyaWdnZXJzIHRoZSBWUlJQIHN3aXRjaG92ZXIsIGFzIHBlciB0aGUgYWJvdmUgZGVzY3Jp
cHRpb24uDQoNCj4gMi4gVGhlIHNvbHV0aW9uIHByb3Bvc2VkIGluIGRyYWZ0LXpob3UtcGltLXZy
cnAgaXMgZGVzaWduZWQgYXMgYSBjb21wbGV0ZQ0KPiBtdWx0aWNhc3QgZmFpbG92ZXIgbWVjaGFu
aXNtOiBpbiBhZGRpdGlvbiB0byBEUiBwcmlvcml0eSBhZGp1c3RtZW50LCB0aGUNCj4gbmV3IGRy
YWZ0IGFkZHJlc3NlcyBvdGhlciBjcml0aWNhbCBwcm9ibGVtcyBpbiBwcm92aWRpbmcgbXVsdGlj
YXN0DQo+IHJlZHVuZGFuY3ksIGluY2x1ZGluZyBBc3NlcnQgbWV0cmljIGFkanVzdG1lbnQsIERG
IGVsZWN0aW9uIGZvciBCaURpcg0KPiBncm91cCBhbmQgdHJhY2tpbmcgbXVsdGlwbGUgVlJSUCBn
cm91cHMuDQoNCg0KPiAzLiBJbiBhZGRpdGlvbiB0byBsYXN0LWhvcCBhbmQgZmlyc3QtaG9wIHNj
ZW5hcmlvLCB0aGUgbmV3IGRyYWZ0IGFkZHJlc3Nlcw0KPiAgdHJhbnNpdCBuZXR3b3JrIHNjZW5h
cmlvIHRvIG1ha2UgTWFzdGVyIHJvdXRlciBwcm9jZXNzIFBJTSBKL1AgZm9yIHRoZQ0KPiB2aXJ0
dWFsIGFkZHJlc3MsIGFuZCBob3cgdG8gbWFpbnRhaW4gb3IgcmVidWlsZCBKL1Agc3RhdGUgd2hl
biBzd2l0Y2hpbmcuDQoNCkNvdWxkIHlvdSBwbGVhc2UgZXhwbGFpbiB0aGUgbW90aXZhdGlvbiBm
b3IgZW5hYmxpbmcgVlJSUCwgcmF0aGVyIHRoYW4gSUdQIGluIHRoZSByZWFsIHRyYW5zaXQgbmV0
d29yayBzY2VuYXJpbz8NCg0KPiBUaGUgb25seSBzaW1pbGFyaXR5IGJldHdlZW4gdGhlIG9sZCBh
bmQgbmV3IGRyYWZ0cyBpcyB0byBtYWtlIG1hc3Rlcg0KPiByb3V0ZXIgdGhlIERSLCB3aGljaCBp
cyBvYnZpb3VzIHdheSB0byBtYWtlIGRlc2lyZWQgcm91dGVyIERSLg0KDQpZZXMsIHRoaXMgaXMg
dGhlIG1ham9yIG1vdGl2YXRpb24gZm9yIGJvdGggZHJhZnRzIGluIG15IHVuZGVyc3RhbmRpbmcu
DQoNCkJlc3QgcmVnYXJkcywNClhpYW9odQ0KDQo+IFRoYW5rcywNCj4gV2VpDQo+IA0KPiANCj4g
DQo+IA0KPiANCj4gDQo+IE9uIDUvMjMvMTMgMjowOCBBTSwgIlByYXNoYW50IEpoaW5ncmFuIChw
amhpbmdyYSkiIDxwamhpbmdyYUBjaXNjby5jb20+DQo+IHdyb3RlOg0KPiANCj4gPkhpIE1pa2Us
DQo+ID4NCj4gPkkgYWdyZWUgd2l0aCBSYWppdiwgYm90aCBkcmFmdHMgYXJlIHRyeWluZyB0byBz
b2x2ZSB0aGUgc2FtZQ0KPiA+aXNzdWUuLi4udGhhdCB0b28gaW4gYWxtb3N0IHNpbWlsYXIgd2F5
Lg0KPiA+DQo+ID4tDQo+ID5SZWdhcmRzLA0KPiA+UHJhc2hhbnQgSmhpbmdyYW4NCj4gPk5PU1RH
IFRNRSAtIFNQIFdpLUZpDQo+ID4NCj4gPmh0dHA6Ly93d3dpbi5jaXNjby5jb20vaW9zL3RlY2gv
bW9iaWxlL3Byb3h5aXB2Ni8NCj4gPmh0dHA6Ly93d3dpbi5jaXNjby5jb20vaW9zL3RlY2gvYnJv
YWRiYW5kDQo+ID4NCj4gPg0KPiA+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPkZyb206
IFJhaml2IEFzYXRpIChyYWppdmEpDQo+ID5TZW50OiBUaHVyc2RheSwgTWF5IDIzLCAyMDEzIDM6
MDYgQU0NCj4gPlRvOiBNaWtlIE1jQnJpZGU7IFh1eGlhb2h1OyBzZ2FuZXNhbkBleHRyZW1lbmV0
d29ya3MuY29tOyBQcmFzaGFudA0KPiA+SmhpbmdyYW4gKHBqaGluZ3JhKTsgV2VpIFpob3UgKHdl
aXpobzIpDQo+ID5DYzogU3RpZyBWZW5hYXM7IHBpbUBpZXRmLm9yZw0KPiA+U3ViamVjdDogUkU6
IFtwaW1dIGNhbGwgZm9yIGFkb3B0aW9uOiBkcmFmdC16aG91LXBpbS12cnJwLTAxDQo+ID4NCj4g
PkhpIE1pa2UsDQo+ID4NCj4gPkl0IHNlZW1zIHRoYXQgYm90aCBkcmFmdHMgc2VlbSB0byBzb2x2
ZSBuZWFybHkgdGhlIHNhbWUgcHJvYmxlbSAobXVsdGlwbGUNCj4gPnJvdXRlcnMgb24gdGhlIG11
bHRpLWFjY2VzcyBpbnRlcmZhY2UgYW5kIGV4aXN0ZW5jZSBvZiBmaXJzdC1ob3ANCj4gPnJlZHVu
ZGFuY3kgcHJvdG9jb2xzIGUuZy4gVlJSUCkuDQo+ID4NCj4gPkNoZWVycywNCj4gPlJhaml2DQo+
ID4NCj4gPg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9tOiBNaWtl
IE1jQnJpZGUgW21haWx0bzptbWNicmlkZTdAZ21haWwuY29tXQ0KPiA+PiBTZW50OiBXZWRuZXNk
YXksIE1heSAyMiwgMjAxMyAyOjE3IEFNDQo+ID4+IFRvOiBYdXhpYW9odTsgc2dhbmVzYW5AZXh0
cmVtZW5ldHdvcmtzLmNvbTsgUmFqaXYgQXNhdGkgKHJhaml2YSk7DQo+ID4+IFByYXNoYW50IEpo
aW5ncmFuIChwamhpbmdyYSk7IFdlaSBaaG91ICh3ZWl6aG8yKQ0KPiA+PiBDYzogU3RpZyBWZW5h
YXM7IE1pa2UgTWNCcmlkZTsgcGltQGlldGYub3JnDQo+ID4+IFN1YmplY3Q6IFJlOiBbcGltXSBj
YWxsIGZvciBhZG9wdGlvbjogZHJhZnQtemhvdS1waW0tdnJycC0wMQ0KPiA+Pg0KPiA+PiBGb2xr
cywNCj4gPj4NCj4gPj4gV2UgaGF2ZSB0aGlzIG5ldyBkcmFmdC16aG91LXBpbS12cnJwLTAxIHdo
aWNoIHdlIGFyZSBhYm91dCB0byBhZG9wdA0KPiA+PiBpbnRvIHRoZSBwaW0gd2cuIEl0IGhhcyBi
ZWVuIGJyb3VnaHQgdG8gdGhlIFdHcyBhdHRlbnRpb24gdGhhdCB0aGVyZQ0KPiA+PiBpcyBhIG9s
ZGVyIGRyYWZ0IChkcmFmdC14dS1waW0tZHJwcmlvcml0eS1hdXRvLWFkanVzdG1lbnQtMDMpIHdo
aWNoDQo+ID4+IG1heSBoYXZlIHNvbWUgb3ZlcmxhcCB3aXRoIHRoZSBuZXcgb25lLiBUaGF0IG9s
ZGVyIGRyYWZ0IGRvZXMgY29udGFpbg0KPiA+PiBpbmZvcm1hdGlvbiBhYm91dCBWUlJQIGF3YXJl
IFBJTSB3aGljaCBpcyBhdHRyaWJ1dGVkIHRvIFN0aWcgaW4gdGhlDQo+ID4+IGFja25vd2xlZGdl
bWVudHMuIElmIHRoZSBmaXZlIG9mIHlvdSBhdXRob3JzIGZlZWwgdGhhdCB0aGVyZSBpcyBzb21l
DQo+ID4+IHZhbGlkaXR5IHRoYXQgdGhlIG9sZGVyIGRyYWZ0IGNvbnRhaW5zIHNvbWUgaW5mb3Jt
YXRpb24gYmVpbmcgdXNlZCBpbg0KPiA+PiB0aGUgbmV3IGRyYWZ0LCB5b3UgbWF5IHdhbnQgdG8g
YWNrbm93bGVkZ2UgdGhhdCBpbiB0aGUgcmVmZXJlbmNlcyBvcg0KPiA+PiBhY2tub3dsZWRnZW1l
bnRzLiBJdCBhcHBlYXJzIHRoZSBkcmFmdHMgYXJlIGRpc3NpbWlsYXIgZW5vdWdoIHRvIG5vdA0K
PiA+PiBiZSBtZXJnZWQgYnV0IEkgbWF5IGJlIHdyb25nLiBQbGVhc2Ugc2hhcmUgeW91ciBvcGlu
aW9ucyBvbiB0aGlzIHNvIHdlDQo+ID4+IGNhbiBlc3RhYmxpc2ggY29uc2Vuc3VzIHdpdGhpbiB0
aGUgZ3JvdXAgYW5kIG1vdmUgdGhlIGRvY3VtZW50IGFsb25nLg0KPiA+Pg0KPiA+PiBJZiB0aGUg
YnJvYWRlciBXRyBwYXJ0aWNpcGFudHMgaGF2ZSBhbiBvcGluaW9uIG9uIHRoaXMgcGxlYXNlIHNw
ZWFrIHVwLg0KPiA+Pg0KPiA+PiB0aGFua3MsDQo+ID4+IG1pa2UNCj4gPj4NCj4gPj4gT24gVGh1
LCBNYXkgOSwgMjAxMyBhdCA3OjMyIFBNLCBYdXhpYW9odSA8eHV4aWFvaHVAaHVhd2VpLmNvbT4g
d3JvdGU6DQo+ID4+ID4gSGkgYWxsLA0KPiA+PiA+DQo+ID4+ID4gVGhpcyBkcmFmdCByZW1pbmRz
IG1lIHRoYXQgdGhlcmUgaGFzIGJlZW4gYSBkcmFmdA0KPiA+PiAoaHR0cDovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQteHUtcGltLWRycHJpb3JpdHktYXV0by1hZGp1c3RtZW50LTAzDQo+ID4+
ICkgdGhyZWUgeWVhcnMgYmVmb3JlIHdoaWNoIHVzZXMgYWxtb3N0IHRoZSBzYW1lIHRlY2hub2xv
Z3kgdG8gc2F2ZQ0KPiA+PiBhbG1vc3QgdGhlIHNhbWUgcHJvYmxlbS4NCj4gPj4gPg0KPiA+PiA+
IFRoZSBmb2xsb3dpbmcgaXMgcXVvdGVkIGZyb20gdGhlIGFib3ZlIGRyYWZ0Og0KPiA+PiA+DQo+
ID4+ID4gICAgIkluIGZhY3QsIGlmIFZSUlAgaXMgcnVuIG9uIHRoZSBQSU0gcm91dGVycyBhbmQg
dGhlIFZSUlAgaGFzDQo+ID4+ZW5hYmxlZA0KPiA+PiA+ICAgIHRoZSB1cHN0cmVhbSBsaW5rIHRy
YWNraW5nIG1lY2hhbmlzbSwgdGhlIFBJTSBEUiBmYWlsb3Zlcg0KPiBtZWNoYW5pc20NCj4gPj4g
PiAgICBjb3VsZCBiZSBjb3VwbGVkIHdpdGggdGhlIFZSUlAgc28gYXMgdG8gcmV1c2UgdGhlIHVw
c3RyZWFtIGxpbmsNCj4gPj4gPiAgICB0cmFja2luZyBtZWNoYW5pc20gb2YgVlJSUC4gT25lIG9w
dGlvbiBpcyB0byBzeW5jaHJvbml6ZSB0aGUgUElNIERSDQo+ID4+ID4gICAgcHJpb3JpdHkgdmFs
dWUgdG8gdGhlIFZSUlAgcHJpb3JpdHkgdmFsdWUgYWx3YXlzLiBJbiB0aGlzIHdheSwgdGhlDQo+
ID4+ID4gICAgUElNIERSIGFuZCB0aGUgVlJSUCBtYXN0ZXIgd2lsbCBhbHdheXMgcnVuIG9uIGFu
IGlkZW50aWNhbCByb3V0ZXINCj4gPj5pZg0KPiA+PiA+ICAgIHRoZSBWUlJQIFByZWVtcHRfTW9k
ZSBpcyBzZXQgdG8gVHJ1ZS4gQW5vdGhlciBvcHRpb24gaXMgdG8gbWFrZSB0aGUNCj4gPj4gPiAg
ICBQSU0gRFIgYW5kIHRoZSBWUlJQIG1hc3RlciBydW4gb24gYW4gaWRlbnRpY2FsIHJvdXRlciBh
bnl3YXkgKGkuZS4sDQo+ID4+ID4gICAgcmVnYXJkbGVzcyB3aGV0aGVyIG9yIG5vdCB0aGUgVlJS
UCBQcmVlbXB0X01vZGUgaXMgVHJ1ZSkuIFRvDQo+ID4+YWNoaWV2ZQ0KPiA+PiA+ICAgIHRoaXMg
Z29hbCwgdGhlIFBJTSBEUiBwcmlvcml0eSBvZiB0aGUgVlJSUCBtYXN0ZXIgcm91dGVyIFNIT1VM
RA0KPiA+PiA+ICAgIGFsd2F5cyBiZSBzZXQgdG8gYSBoaWdoZXIgZml4ZWQgdmFsdWUgdGhhbiB0
aGF0IG9mIHRoZSBWUlJQIHNsYXZlDQo+ID4+ID4gICAgcm91dGVyIGF1dG9tYXRpY2FsbHkuIg0K
PiA+PiA+DQo+ID4+ID4gQmVzdCByZWdhcmRzLA0KPiA+PiA+IFhpYW9odQ0KPiA+PiA+DQo+ID4+
ID4+IC0tLS0t08q8/tStvP4tLS0tLQ0KPiA+PiA+PiC3orz+yMs6IHBpbS1ib3VuY2VzQGlldGYu
b3JnIFttYWlsdG86cGltLWJvdW5jZXNAaWV0Zi5vcmddILT6se0NCj4gPj4gTWlrZQ0KPiA+PiA+
PiBNY0JyaWRlDQo+ID4+ID4+ILeiy83KsbzkOiAyMDEzxOo11MIxMMjVIDM6NDgNCj4gPj4gPj4g
ytW8/sjLOiBwaW1AaWV0Zi5vcmcNCj4gPj4gPj4g1vfM4jogW3BpbV0gY2FsbCBmb3IgYWRvcHRp
b246IGRyYWZ0LXpob3UtcGltLXZycnAtMDENCj4gPj4gPj4NCj4gPj4gPj4gZHJhZnQtemhvdS1w
aW0tdnJycC0wMSB3YXMgcHJlc2VudGVkIGluIG91ciBtb3N0IHJlY2VudCBwaW0gbWVldGluZw0K
PiA+PiA+PiBpbiBPcmxhbmRvLiA0IHBlb3BsZSB3ZXJlIGluIGZhdm9yIG9mIGFkb3B0aW5nIHRo
ZSBkcmFmdC4gWmVybw0KPiA+PmFnYWluc3QuDQo+ID4+ID4+IFBsZWFzZSByZWFkIHRoZSBkcmFm
dCAoaXRzIHNob3J0KSBhbmQgcHJvdmlkZSBhbiBvcGluaW9uIGVpdGhlciB3YXkNCj4gPj4gPj4g
YnkgdGhlIGVuZCBvZiBuZXh0IEZyaWRheSB0aGUgMTd0aC4NCj4gPj4gPj4NCj4gPj4gPj4gaHR0
cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC16aG91LXBpbS12cnJwLTAxLnR4dA0KPiA+PiA+Pg0K
PiA+PiA+PiB0aGFua3MsDQo+ID4+ID4+IG1pa2UNCj4gPj4gPj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj4gPj4gcGltIG1haWxpbmcgbGlzdA0K
PiA+PiA+PiBwaW1AaWV0Zi5vcmcNCj4gPj4gPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9waW0NCg0K

From kurapati@juniper.net  Fri May 24 06:59:03 2013
Return-Path: <kurapati@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72A7B21F9029; Fri, 24 May 2013 06:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.111
X-Spam-Level: 
X-Spam-Status: No, score=-3.111 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_6CONS_WORD=0.356, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73iulMCL7DXc; Fri, 24 May 2013 06:58:57 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id BA12E21F8FD0; Fri, 24 May 2013 06:58:56 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUZ9yFs6SOAa0GyTUGwpL8gwfZ4HR7/xF@postini.com; Fri, 24 May 2013 06:58:56 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 24 May 2013 06:57:10 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Fri, 24 May 2013 06:57:10 -0700
Received: from co1outboundpool.messaging.microsoft.com (216.32.180.185) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 24 May 2013 07:00:45 -0700
Received: from mail41-co1-R.bigfish.com (10.243.78.249) by CO1EHSOBE038.bigfish.com (10.243.66.103) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 13:57:09 +0000
Received: from mail41-co1 (localhost [127.0.0.1])	by mail41-co1-R.bigfish.com (Postfix) with ESMTP id 776FAA60111; Fri, 24 May 2013 13:57:09 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:132.245.2.21; KIP:(null); UIP:(null); (null); H:BN1PRD0512HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -24
X-BigFish: PS-24(zz9371I936eI542I4015Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz31h2a8h668h839h93fhd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1dc1h1155h)
Received-SPF: softfail (mail41-co1: transitioning domain of juniper.net does not designate 132.245.2.21 as permitted sender) client-ip=132.245.2.21; envelope-from=kurapati@juniper.net; helo=BN1PRD0512HT001.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail41-co1 (localhost.localdomain [127.0.0.1]) by mail41-co1 (MessageSwitch) id 136940382841738_9253; Fri, 24 May 2013 13:57:08 +0000 (UTC)
Received: from CO1EHSMHS010.bigfish.com (unknown [10.243.78.227])	by mail41-co1.bigfish.com (Postfix) with ESMTP id F2904240062; Fri, 24 May 2013 13:57:07 +0000 (UTC)
Received: from BN1PRD0512HT001.namprd05.prod.outlook.com (132.245.2.21) by CO1EHSMHS010.bigfish.com (10.243.66.20) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 24 May 2013 13:57:07 +0000
Received: from BN1PRD0512MB666.namprd05.prod.outlook.com ([169.254.12.105]) by BN1PRD0512HT001.namprd05.prod.outlook.com ([10.255.193.34]) with mapi id 14.16.0311.000; Fri, 24 May 2013 13:56:58 +0000
From: Pavan Kurapati <kurapati@juniper.net>
To: "l3vpn@ietf.org" <l3vpn@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: New Version Notification for draft-kurapati-dynamicrp-bgpmvpn-00.txt
Thread-Index: AQHOWApt2f1e6uS8Ckiq+Yr62KE3GpkUWsmA
Date: Fri, 24 May 2013 13:56:58 +0000
Message-ID: <DD09F2DB562A004DA192984350EA9A2E0EB2DA70@BN1PRD0512MB666.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%ATT.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: Marco Rodrigues <marco@juniper.net>, "ASIF, SAUD" <sa9362@att.com>
Subject: [pim] FW: New Version Notification for draft-kurapati-dynamicrp-bgpmvpn-00.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 24 May 2013 13:59:03 -0000

SGksDQpXZSBwdWJsaXNoZWQgYSBuZXcgZHJhZnQgZm9yIGVuY29kaW5nIEJTUiBpbmZvcm1hdGlv
biBpbiBCR1AgZm9yIEJHUC1NVlBOIGJhc2VkIGRlcGxveW1lbnRzLiBQbGVhc2UgcmV2aWV3IGFu
ZCBsZXQgdXMga25vdyB5b3VyIGZlZWRiYWNrLg0KDQpodHRwOi8vd3d3LmlldGYub3JnL2lkL2Ry
YWZ0LWt1cmFwYXRpLWR5bmFtaWNycC1iZ3BtdnBuLTAwLnR4dA0KDQoNClRoYW5rcywNClBhdmFu
DQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGludGVybmV0LWRyYWZ0c0Bp
ZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQpTZW50OiBUaHVyc2Rh
eSwgTWF5IDIzLCAyMDEzIDc6MDggUE0NClRvOiBQYXZhbiBLdXJhcGF0aTsgTWFyY28gUm9kcmln
dWVzOyBTYXVkIEFzaWY7IEt1cnQgV2luZGlzY2gNClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlm
aWNhdGlvbiBmb3IgZHJhZnQta3VyYXBhdGktZHluYW1pY3JwLWJncG12cG4tMDAudHh0DQoNCg0K
QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWt1cmFwYXRpLWR5bmFtaWNycC1iZ3BtdnBuLTAw
LnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBQYXZhbiBLdXJhcGF0aSBh
bmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOgkgZHJhZnQta3Vy
YXBhdGktZHluYW1pY3JwLWJncG12cG4NClJldmlzaW9uOgkgMDANClRpdGxlOgkJIER5bmFtaWMg
UlAgZW5jb2RpbmdzIGluIEJHUCBiYXNlZCBNVlBOcw0KQ3JlYXRpb24gZGF0ZToJIDIwMTMtMDUt
MjQNCkdyb3VwOgkJIEluZGl2aWR1YWwgU3VibWlzc2lvbg0KTnVtYmVyIG9mIHBhZ2VzOiAyMA0K
VVJMOiAgICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFm
dC1rdXJhcGF0aS1keW5hbWljcnAtYmdwbXZwbi0wMC50eHQNClN0YXR1czogICAgICAgICAgaHR0
cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1rdXJhcGF0aS1keW5hbWljcnAtYmdw
bXZwbg0KSHRtbGl6ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1r
dXJhcGF0aS1keW5hbWljcnAtYmdwbXZwbi0wMA0KDQoNCkFic3RyYWN0Og0KICAgUElNIEdyb3Vw
LXRvLVJQIG1hcHBpbmdzIGFyZSBkaXN0cmlidXRlZCBkeW5hbWljYWxseSB1c2luZyBwcm90b2Nv
bHMNCiAgIHN1Y2ggYXMgQlNSIG9yIEF1dG8tUlAuICBUaGUgQkdQLU1WUE4gc3BlY2lmaWNhdGlv
biBwcm92aWRlcyBmb3IgdGhpcw0KICAgaW5mb3JtYXRpb24gdG8gYmUgZW5jYXBzdWxhdGVkIGlu
IGFuIEktUE1TSSBvciBTLVBNU0kgcHJvdmlkZXIgdHVubmVsDQogICBiZXR3ZWVuIHRoZSBQRXMg
aW4gYW4gTVZQTiBlbnZpcm9ubWVudC4gIFNpbmNlIHRoaXMgaXMgY29udHJvbA0KICAgaW5mb3Jt
YXRpb24sIGl0IGlzIGRlc2lyYWJsZSB0byBzaWduYWwgdGhpcyBpbmZvcm1hdGlvbiBpbiBCR1AN
CiAgIGJldHdlZW4gUEVzLCBzaW1pbGFyIHRvIGNhcnJ5aW5nIG90aGVyIGN1c3RvbWVyIGNvbnRy
b2wgc3RhdGUgc3VjaCBhcw0KICAgQy1NdWx0aWNhc3Qgcm91dGVzLiAgVGhpcyBkb2N1bWVudCBz
cGVjaWZpZXMgdGhlIG1lY2hhbmlzbXMgYW5kDQogICBwcm9jZWR1cmVzIHRvIGNhcnJ5IGJvb3Rz
dHJhcCBpbmZvcm1hdGlvbiB2aWEgQkdQIHRvIHByb3ZpZGUgdHJ1ZQ0KICAgY29udHJvbCBhbmQg
ZGF0YSBwbGFuZSBzZXBhcmF0aW9uLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0K
VGhlIElFVEYgU2VjcmV0YXJpYXQNCg0KDQo=


From weizho2@cisco.com  Thu May 23 15:21:44 2013
Return-Path: <weizho2@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF33A21F984D for <pim@ietfa.amsl.com>; Thu, 23 May 2013 15:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.057
X-Spam-Level: 
X-Spam-Status: No, score=-6.057 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xowpP+wwFF0N for <pim@ietfa.amsl.com>; Thu, 23 May 2013 15:21:30 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id A579521F86F0 for <pim@ietf.org>; Thu, 23 May 2013 14:36:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8142; q=dns/txt; s=iport; t=1369344985; x=1370554585; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=iG4Ue3g4PgHox3fSfqteV1phNBLykJJmsKKja34llsU=; b=KQREdJFg0Xl6cKOlwho9YsjaiDkXZXHKGRj1ypGpzmN+G0gsMlaDf6MB gn3oqstkjKBqvQp8wsX4JXjQX4gG32LhFDW6vFmeX2vYFSNagRB68z3Kc 4rj48wUTum0im7usSnLkb+2gEEatRNz1MYeJ1OvBlDIgBuiL6F3ru7JqW M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcGAAOJnlGtJV2d/2dsb2JhbABZgwgwgzu+dA1/FnSCIwEBAQQBAQEaFzoLDAYBBgIRBAEBAQQGHQUEHwYLFAkIAgQBDQUIARKHYAMPDIx+myAIiHINiEqBIoskgSWBAQ8HGwcGgjc2YQOVVYMPinSFI4MPgXE1
X-IronPort-AV: E=Sophos;i="4.87,730,1363132800"; d="scan'208";a="214332754"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-8.cisco.com with ESMTP; 23 May 2013 21:36:25 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4NLaOum017090 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 May 2013 21:36:25 GMT
Received: from xmb-rcd-x05.cisco.com ([169.254.15.201]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Thu, 23 May 2013 16:36:24 -0500
From: "Wei Zhou (weizho2)" <weizho2@cisco.com>
To: "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>, "Rajiv Asati (rajiva)" <rajiva@cisco.com>, Mike McBride <mmcbride7@gmail.com>, Xuxiaohu <xuxiaohu@huawei.com>, "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOVrP+uggkeQnYAUax3C6a4z91JZkSDz2AgADBXYCAAFucAA==
Date: Thu, 23 May 2013 21:36:23 +0000
Message-ID: <23EF39780ADBDE42806FAEE7B8578690183E4D44@xmb-rcd-x05.cisco.com>
In-Reply-To: <F567B77E0728694BB6716DB3C9000B6B12ABC487@xmb-rcd-x14.cisco.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.209.193]
Content-Type: text/plain; charset="gb2312"
Content-ID: <9D9A78B69760A44FA7A7D92047F6723E@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 24 May 2013 09:37:52 -0700
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 23 May 2013 22:44:37 -0000

SGksDQoNClRoYW5rIHlvdSBhbGwgZm9yIHByb3ZpZGluZyBjb21tZW50cyBhbmQgdGhlIGluZm9y
bWF0aW9uIG9uDQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14dS1waW0tZHJwcmlv
cml0eS1hdXRvLWFkanVzdG1lbnQtMDMuDQoNCkkganVzdCByZWFkIHRocm91Z2ggdGhlIGRyYWZ0
IHByb3Bvc2VkIGJ5IHhpYW9odSBhcyBJIHdhcyBub3QgYXdhcmUgb2YNCnRoaXMgZHJhZnQgdW50
aWwgeGlhb2h1IGtpbmRseSBtZW50aW9uZWQgaW4gdGhlIG1haWwgbGlzdC4gQWZ0ZXIgY2FyZWZ1
bGx5DQpjb21wYXJpbmcgdGhlIHR3byBkcmFmdHMsIGxldCBtZSB0cnkgZXhwbGFpbiB0aGUgZGlm
ZmVyZW5jZXMgYmV0d2VlbiB0aGVtDQoocmVmZXJyZWQgYXMgZHJhZnQteHUtZHItYWRqIGFuZCBk
cmFmdC16aG91LXBpbS12cnJwKToNCg0KMS4gVGhlIG9yaWdpbmFsIHByb2JsZW1zIHRoYXQgdHdv
IGRyYWZ0cyB0cnkgdG8gc29sdmUgbWlnaHQgbG9vayBzaW1pbGFyDQpidXQgdGhleSBhcmUgYWN0
dWFsbHkgcXVpdGUgZGlmZmVyZW50IGluIHRoZSBmb2xsb3dpbmcgd2F5Og0KZHJhZnQteHUtZHIt
YWRqIHRhcmdldHMgdGhlIFBJTSBEUiBhdXRvLWFkanVzdG1lbnQgYmFzZWQgb24gdXBzdHJlYW0g
bGluaw0KdHJhY2tpbmcsIHdoaWxlIHRoZSBpZGVhIGluIGRyYWZ0LXpob3UtcGltLXZycnAgaXMg
dG8gcHJvdmlkZSBhIGNvbXBsZXRlDQpzb2x1dGlvbiB0byBlbmFibGUgbXVsdGljYXN0IHRvIGlu
dGVyb3BlcmF0ZSB3aXRoIGZpcnN0IGhvcCByZWR1bmRhbmN5DQpwcm90b2NvbCBpbiByZXNwb25z
ZSB0byBhbnkgaW50ZXJlc3RlZCBldmVudHM6IE1hc3RlciByb3V0ZXJzIGdvZXMgZG93biwNCnVw
c3RyZWFtIGxpbmsgdXAvZG93biwgYmFuZHdpZHRoIGNoYW5nZSBhbmQgb3RoZXIgbG9naWNhbCBv
YmplY3RzIHRoYXQNClZSUlAgY291bGQgdHJhY2suDQoNCjIuIFRoZSBzb2x1dGlvbiBwcm9wb3Nl
ZCBpbiBkcmFmdC16aG91LXBpbS12cnJwIGlzIGRlc2lnbmVkIGFzIGEgY29tcGxldGUNCm11bHRp
Y2FzdCBmYWlsb3ZlciBtZWNoYW5pc206IGluIGFkZGl0aW9uIHRvIERSIHByaW9yaXR5IGFkanVz
dG1lbnQsIHRoZQ0KbmV3IGRyYWZ0IGFkZHJlc3NlcyBvdGhlciBjcml0aWNhbCBwcm9ibGVtcyBp
biBwcm92aWRpbmcgbXVsdGljYXN0DQpyZWR1bmRhbmN5LCBpbmNsdWRpbmcgQXNzZXJ0IG1ldHJp
YyBhZGp1c3RtZW50LCBERiBlbGVjdGlvbiBmb3IgQmlEaXINCmdyb3VwIGFuZCB0cmFja2luZyBt
dWx0aXBsZSBWUlJQIGdyb3Vwcy4NCg0KMy4gSW4gYWRkaXRpb24gdG8gbGFzdC1ob3AgYW5kIGZp
cnN0LWhvcCBzY2VuYXJpbywgdGhlIG5ldyBkcmFmdCBhZGRyZXNzZXMNCiB0cmFuc2l0IG5ldHdv
cmsgc2NlbmFyaW8gdG8gbWFrZSBNYXN0ZXIgcm91dGVyIHByb2Nlc3MgUElNIEovUCBmb3IgdGhl
DQp2aXJ0dWFsIGFkZHJlc3MsIGFuZCBob3cgdG8gbWFpbnRhaW4gb3IgcmVidWlsZCBKL1Agc3Rh
dGUgd2hlbiBzd2l0Y2hpbmcuDQoNClRoZSBvbmx5IHNpbWlsYXJpdHkgYmV0d2VlbiB0aGUgb2xk
IGFuZCBuZXcgZHJhZnRzIGlzIHRvIG1ha2UgbWFzdGVyDQpyb3V0ZXIgdGhlIERSLCB3aGljaCBp
cyBvYnZpb3VzIHdheSB0byBtYWtlIGRlc2lyZWQgcm91dGVyIERSLg0KDQpUaGFua3MsDQpXZWkN
Cg0KDQoNCg0KDQoNCk9uIDUvMjMvMTMgMjowOCBBTSwgIlByYXNoYW50IEpoaW5ncmFuIChwamhp
bmdyYSkiIDxwamhpbmdyYUBjaXNjby5jb20+DQp3cm90ZToNCg0KPkhpIE1pa2UsDQo+DQo+SSBh
Z3JlZSB3aXRoIFJhaml2LCBib3RoIGRyYWZ0cyBhcmUgdHJ5aW5nIHRvIHNvbHZlIHRoZSBzYW1l
DQo+aXNzdWUuLi4udGhhdCB0b28gaW4gYWxtb3N0IHNpbWlsYXIgd2F5Lg0KPg0KPi0NCj5SZWdh
cmRzLA0KPlByYXNoYW50IEpoaW5ncmFuDQo+Tk9TVEcgVE1FIC0gU1AgV2ktRmkNCj4NCj5odHRw
Oi8vd3d3aW4uY2lzY28uY29tL2lvcy90ZWNoL21vYmlsZS9wcm94eWlwdjYvDQo+aHR0cDovL3d3
d2luLmNpc2NvLmNvbS9pb3MvdGVjaC9icm9hZGJhbmQNCj4NCj4NCj4tLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPkZyb206IFJhaml2IEFzYXRpIChyYWppdmEpDQo+U2VudDogVGh1cnNkYXks
IE1heSAyMywgMjAxMyAzOjA2IEFNDQo+VG86IE1pa2UgTWNCcmlkZTsgWHV4aWFvaHU7IHNnYW5l
c2FuQGV4dHJlbWVuZXR3b3Jrcy5jb207IFByYXNoYW50DQo+SmhpbmdyYW4gKHBqaGluZ3JhKTsg
V2VpIFpob3UgKHdlaXpobzIpDQo+Q2M6IFN0aWcgVmVuYWFzOyBwaW1AaWV0Zi5vcmcNCj5TdWJq
ZWN0OiBSRTogW3BpbV0gY2FsbCBmb3IgYWRvcHRpb246IGRyYWZ0LXpob3UtcGltLXZycnAtMDEN
Cj4NCj5IaSBNaWtlLA0KPg0KPkl0IHNlZW1zIHRoYXQgYm90aCBkcmFmdHMgc2VlbSB0byBzb2x2
ZSBuZWFybHkgdGhlIHNhbWUgcHJvYmxlbSAobXVsdGlwbGUNCj5yb3V0ZXJzIG9uIHRoZSBtdWx0
aS1hY2Nlc3MgaW50ZXJmYWNlIGFuZCBleGlzdGVuY2Ugb2YgZmlyc3QtaG9wDQo+cmVkdW5kYW5j
eSBwcm90b2NvbHMgZS5nLiBWUlJQKS4NCj4NCj5DaGVlcnMsDQo+UmFqaXYNCj4NCj4NCj4+IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiBGcm9tOiBNaWtlIE1jQnJpZGUgW21haWx0bzpt
bWNicmlkZTdAZ21haWwuY29tXQ0KPj4gU2VudDogV2VkbmVzZGF5LCBNYXkgMjIsIDIwMTMgMjox
NyBBTQ0KPj4gVG86IFh1eGlhb2h1OyBzZ2FuZXNhbkBleHRyZW1lbmV0d29ya3MuY29tOyBSYWpp
diBBc2F0aSAocmFqaXZhKTsNCj4+IFByYXNoYW50IEpoaW5ncmFuIChwamhpbmdyYSk7IFdlaSBa
aG91ICh3ZWl6aG8yKQ0KPj4gQ2M6IFN0aWcgVmVuYWFzOyBNaWtlIE1jQnJpZGU7IHBpbUBpZXRm
Lm9yZw0KPj4gU3ViamVjdDogUmU6IFtwaW1dIGNhbGwgZm9yIGFkb3B0aW9uOiBkcmFmdC16aG91
LXBpbS12cnJwLTAxDQo+PiANCj4+IEZvbGtzLA0KPj4gDQo+PiBXZSBoYXZlIHRoaXMgbmV3IGRy
YWZ0LXpob3UtcGltLXZycnAtMDEgd2hpY2ggd2UgYXJlIGFib3V0IHRvIGFkb3B0DQo+PiBpbnRv
IHRoZSBwaW0gd2cuIEl0IGhhcyBiZWVuIGJyb3VnaHQgdG8gdGhlIFdHcyBhdHRlbnRpb24gdGhh
dCB0aGVyZQ0KPj4gaXMgYSBvbGRlciBkcmFmdCAoZHJhZnQteHUtcGltLWRycHJpb3JpdHktYXV0
by1hZGp1c3RtZW50LTAzKSB3aGljaA0KPj4gbWF5IGhhdmUgc29tZSBvdmVybGFwIHdpdGggdGhl
IG5ldyBvbmUuIFRoYXQgb2xkZXIgZHJhZnQgZG9lcyBjb250YWluDQo+PiBpbmZvcm1hdGlvbiBh
Ym91dCBWUlJQIGF3YXJlIFBJTSB3aGljaCBpcyBhdHRyaWJ1dGVkIHRvIFN0aWcgaW4gdGhlDQo+
PiBhY2tub3dsZWRnZW1lbnRzLiBJZiB0aGUgZml2ZSBvZiB5b3UgYXV0aG9ycyBmZWVsIHRoYXQg
dGhlcmUgaXMgc29tZQ0KPj4gdmFsaWRpdHkgdGhhdCB0aGUgb2xkZXIgZHJhZnQgY29udGFpbnMg
c29tZSBpbmZvcm1hdGlvbiBiZWluZyB1c2VkIGluDQo+PiB0aGUgbmV3IGRyYWZ0LCB5b3UgbWF5
IHdhbnQgdG8gYWNrbm93bGVkZ2UgdGhhdCBpbiB0aGUgcmVmZXJlbmNlcyBvcg0KPj4gYWNrbm93
bGVkZ2VtZW50cy4gSXQgYXBwZWFycyB0aGUgZHJhZnRzIGFyZSBkaXNzaW1pbGFyIGVub3VnaCB0
byBub3QNCj4+IGJlIG1lcmdlZCBidXQgSSBtYXkgYmUgd3JvbmcuIFBsZWFzZSBzaGFyZSB5b3Vy
IG9waW5pb25zIG9uIHRoaXMgc28gd2UNCj4+IGNhbiBlc3RhYmxpc2ggY29uc2Vuc3VzIHdpdGhp
biB0aGUgZ3JvdXAgYW5kIG1vdmUgdGhlIGRvY3VtZW50IGFsb25nLg0KPj4gDQo+PiBJZiB0aGUg
YnJvYWRlciBXRyBwYXJ0aWNpcGFudHMgaGF2ZSBhbiBvcGluaW9uIG9uIHRoaXMgcGxlYXNlIHNw
ZWFrIHVwLg0KPj4gDQo+PiB0aGFua3MsDQo+PiBtaWtlDQo+PiANCj4+IE9uIFRodSwgTWF5IDks
IDIwMTMgYXQgNzozMiBQTSwgWHV4aWFvaHUgPHh1eGlhb2h1QGh1YXdlaS5jb20+IHdyb3RlOg0K
Pj4gPiBIaSBhbGwsDQo+PiA+DQo+PiA+IFRoaXMgZHJhZnQgcmVtaW5kcyBtZSB0aGF0IHRoZXJl
IGhhcyBiZWVuIGEgZHJhZnQNCj4+IChodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14
dS1waW0tZHJwcmlvcml0eS1hdXRvLWFkanVzdG1lbnQtMDMNCj4+ICkgdGhyZWUgeWVhcnMgYmVm
b3JlIHdoaWNoIHVzZXMgYWxtb3N0IHRoZSBzYW1lIHRlY2hub2xvZ3kgdG8gc2F2ZQ0KPj4gYWxt
b3N0IHRoZSBzYW1lIHByb2JsZW0uDQo+PiA+DQo+PiA+IFRoZSBmb2xsb3dpbmcgaXMgcXVvdGVk
IGZyb20gdGhlIGFib3ZlIGRyYWZ0Og0KPj4gPg0KPj4gPiAgICAiSW4gZmFjdCwgaWYgVlJSUCBp
cyBydW4gb24gdGhlIFBJTSByb3V0ZXJzIGFuZCB0aGUgVlJSUCBoYXMNCj4+ZW5hYmxlZA0KPj4g
PiAgICB0aGUgdXBzdHJlYW0gbGluayB0cmFja2luZyBtZWNoYW5pc20sIHRoZSBQSU0gRFIgZmFp
bG92ZXIgbWVjaGFuaXNtDQo+PiA+ICAgIGNvdWxkIGJlIGNvdXBsZWQgd2l0aCB0aGUgVlJSUCBz
byBhcyB0byByZXVzZSB0aGUgdXBzdHJlYW0gbGluaw0KPj4gPiAgICB0cmFja2luZyBtZWNoYW5p
c20gb2YgVlJSUC4gT25lIG9wdGlvbiBpcyB0byBzeW5jaHJvbml6ZSB0aGUgUElNIERSDQo+PiA+
ICAgIHByaW9yaXR5IHZhbHVlIHRvIHRoZSBWUlJQIHByaW9yaXR5IHZhbHVlIGFsd2F5cy4gSW4g
dGhpcyB3YXksIHRoZQ0KPj4gPiAgICBQSU0gRFIgYW5kIHRoZSBWUlJQIG1hc3RlciB3aWxsIGFs
d2F5cyBydW4gb24gYW4gaWRlbnRpY2FsIHJvdXRlcg0KPj5pZg0KPj4gPiAgICB0aGUgVlJSUCBQ
cmVlbXB0X01vZGUgaXMgc2V0IHRvIFRydWUuIEFub3RoZXIgb3B0aW9uIGlzIHRvIG1ha2UgdGhl
DQo+PiA+ICAgIFBJTSBEUiBhbmQgdGhlIFZSUlAgbWFzdGVyIHJ1biBvbiBhbiBpZGVudGljYWwg
cm91dGVyIGFueXdheSAoaS5lLiwNCj4+ID4gICAgcmVnYXJkbGVzcyB3aGV0aGVyIG9yIG5vdCB0
aGUgVlJSUCBQcmVlbXB0X01vZGUgaXMgVHJ1ZSkuIFRvDQo+PmFjaGlldmUNCj4+ID4gICAgdGhp
cyBnb2FsLCB0aGUgUElNIERSIHByaW9yaXR5IG9mIHRoZSBWUlJQIG1hc3RlciByb3V0ZXIgU0hP
VUxEDQo+PiA+ICAgIGFsd2F5cyBiZSBzZXQgdG8gYSBoaWdoZXIgZml4ZWQgdmFsdWUgdGhhbiB0
aGF0IG9mIHRoZSBWUlJQIHNsYXZlDQo+PiA+ICAgIHJvdXRlciBhdXRvbWF0aWNhbGx5LiINCj4+
ID4NCj4+ID4gQmVzdCByZWdhcmRzLA0KPj4gPiBYaWFvaHUNCj4+ID4NCj4+ID4+IC0tLS0t08q8
/tStvP4tLS0tLQ0KPj4gPj4gt6K8/sjLOiBwaW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnBp
bS1ib3VuY2VzQGlldGYub3JnXSC0+rHtDQo+PiBNaWtlDQo+PiA+PiBNY0JyaWRlDQo+PiA+PiC3
osvNyrG85DogMjAxM8TqNdTCMTDI1SAzOjQ4DQo+PiA+PiDK1bz+yMs6IHBpbUBpZXRmLm9yZw0K
Pj4gPj4g1vfM4jogW3BpbV0gY2FsbCBmb3IgYWRvcHRpb246IGRyYWZ0LXpob3UtcGltLXZycnAt
MDENCj4+ID4+DQo+PiA+PiBkcmFmdC16aG91LXBpbS12cnJwLTAxIHdhcyBwcmVzZW50ZWQgaW4g
b3VyIG1vc3QgcmVjZW50IHBpbSBtZWV0aW5nDQo+PiA+PiBpbiBPcmxhbmRvLiA0IHBlb3BsZSB3
ZXJlIGluIGZhdm9yIG9mIGFkb3B0aW5nIHRoZSBkcmFmdC4gWmVybw0KPj5hZ2FpbnN0Lg0KPj4g
Pj4gUGxlYXNlIHJlYWQgdGhlIGRyYWZ0IChpdHMgc2hvcnQpIGFuZCBwcm92aWRlIGFuIG9waW5p
b24gZWl0aGVyIHdheQ0KPj4gPj4gYnkgdGhlIGVuZCBvZiBuZXh0IEZyaWRheSB0aGUgMTd0aC4N
Cj4+ID4+DQo+PiA+PiBodHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LXpob3UtcGltLXZycnAt
MDEudHh0DQo+PiA+Pg0KPj4gPj4gdGhhbmtzLA0KPj4gPj4gbWlrZQ0KPj4gPj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+ID4+IHBpbSBtYWlsaW5n
IGxpc3QNCj4+ID4+IHBpbUBpZXRmLm9yZw0KPj4gPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9waW0NCg0K

From stig@venaas.com  Tue May 28 11:28:08 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC1A11E80EA for <pim@ietfa.amsl.com>; Tue, 28 May 2013 11:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8V-xx8qm5ai5 for <pim@ietfa.amsl.com>; Tue, 28 May 2013 11:28:03 -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 631C611E80E0 for <pim@ietf.org>; Tue, 28 May 2013 11:28:03 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 8803E8117 for <pim@ietf.org>; Tue, 28 May 2013 20:27:58 +0200 (CEST)
Message-ID: <51A4F72C.9040507@venaas.com>
Date: Tue, 28 May 2013 11:27:56 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: pim@ietf.org
References: <519BA747.1030201@venaas.com>
In-Reply-To: <519BA747.1030201@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [pim] Reminder: pim WGLC for draft-ietf-pim-rfc4601-update-survey-report-00
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 28 May 2013 18:28:08 -0000

This last call ends Sunday, we need more people to review this.

Stig

On 5/21/2013 9:56 AM, Stig Venaas wrote:
> Hi
>
> We, the chairs, want to speed up the process of updating RFC 4601
> and as a next step we want to make sure that you, the working group,
> are happy with the implementation report. Once the group is happy, we
> want to get the report published, and then finalize the updates to
> 4601 based on that.
>
> The report results have been presented to the group. There were some
> comments in the adoption call, and the adopted version took them into
> account. The draft is available at
> http://tools.ietf.org/html/draft-ietf-pim-rfc4601-update-survey-report-00
>
> With this email we're starting a working group last call, ending
> Sunday June 2nd. This is important work and we need your review. It
> is the bases for updating one of our core RFCs, please read through
> the report and tell us whether it is ready to be published.
>
> Stig
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From weizho2@cisco.com  Tue May 28 13:47:02 2013
Return-Path: <weizho2@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA8EB21F946C for <pim@ietfa.amsl.com>; Tue, 28 May 2013 13:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.057
X-Spam-Level: 
X-Spam-Status: No, score=-6.057 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w03XFIoyeYD6 for <pim@ietfa.amsl.com>; Tue, 28 May 2013 13:46:57 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id CB2F021F9416 for <pim@ietf.org>; Tue, 28 May 2013 13:46:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11660; q=dns/txt; s=iport; t=1369774016; x=1370983616; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ff5MTmJ1eDDcKRshqDi+rGJ5BlfynsM3idOtWOu9e44=; b=Fxt8vr0r4Jda80LYPhsdQiyyNWNN5IowQ5iKwPsmgYzC/Fw7UPiAhDmi f3/D7xRhCWHk2/eZ3+0bchqnuhlSKPhxjvA/ZgcZml9KkvUovuuVPOnbT /kNv7Fug0CGI+gofSxJwjhm9yiXzUMXUeSz8sOnxg8vVMbwn0tlqZyq79 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlQGAP4WpVGtJXG8/2dsb2JhbABZgwgwgzu+Zw15FnSCIwEBAQQBAQEaFzoLDAYBBgIRBAEBAQQGHQUEHwYLFAkIAgQBDQUIARKHYAMPDI5QmyIIiQANiFGBIoskgSWBARYbBwaCNzZhA5VVgw+KdIUjgw+BcTY
X-IronPort-AV: E=Sophos;i="4.87,759,1363132800"; d="scan'208";a="215922608"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 28 May 2013 20:46:55 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4SKks2G015609 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 May 2013 20:46:54 GMT
Received: from xmb-rcd-x05.cisco.com ([169.254.15.201]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Tue, 28 May 2013 15:46:54 -0500
From: "Wei Zhou (weizho2)" <weizho2@cisco.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>, "Rajiv Asati (rajiva)" <rajiva@cisco.com>, Mike McBride <mmcbride7@gmail.com>, "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOVrP+uggkeQnYAUax3C6a4z91JZkSDz2AgADBXYCAAFucAIAAvfgAgAcP4wA=
Date: Tue, 28 May 2013 20:46:53 +0000
Message-ID: <23EF39780ADBDE42806FAEE7B8578690183E54D2@xmb-rcd-x05.cisco.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081C2A89@NKGEML512-MBS.china.huawei.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.209.193]
Content-Type: text/plain; charset="gb2312"
Content-ID: <0602DD1BEC80E24B9BD77B96752ECC80@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 28 May 2013 20:47:02 -0000

SGksIFhpYW9odQ0KDQpUaGUgbW90aXZhdGUgZm9yIGVuYWJsaW5nIFZSUlAsIHJhdGhlciB0aGFu
IElHUCBpbiB0aGUgcmVhbCB0cmFuc2l0DQpuZXR3b3JrIGlzIHRvIGFkZHJlc3MgdGhlIGZvbGxv
d2luZyBzY2VuYXJpb3M6IDEpIHR3byBQSU0gZG9tYWlucyBpbg0KZGlmZmVyZW50IHN1Ym5ldHMg
KHBvc3NpYmx5IHdpdGggZmlyZXdhbGwgaW4gYmV0d2VlbiksIG9yIDIpIGluIGEgc2luZ2xlDQpz
dWJuZXQgd2hlcmUgdGhlIHByb3ZpZGVyIGRvZXMgbm90IHdpc2ggdG8gcnVuIGEgcm91dGluZyBw
cm90b2NvbCBiZXR3ZWVuDQp0aGUgcHJvdmlkZXIncyBuZXR3b3JrIGFuZCBjdXN0b21lciBuZXR3
b3Jrcy4NCg0KDQpUaGFua3MsDQpXZWkNCg0KDQoNCg0KDQpPbiA1LzIzLzEzIDY6NTYgUE0sICJY
dXhpYW9odSIgPHh1eGlhb2h1QGh1YXdlaS5jb20+IHdyb3RlOg0KDQo+SGksDQo+DQo+PiAtLS0t
LdPKvP7Urbz+LS0tLS0NCj4+ILeivP7IyzogV2VpIFpob3UgKHdlaXpobzIpIFttYWlsdG86d2Vp
emhvMkBjaXNjby5jb21dDQo+PiC3osvNyrG85DogMjAxM8TqNdTCMjTI1SA1OjM2DQo+PiDK1bz+
yMs6IFByYXNoYW50IEpoaW5ncmFuIChwamhpbmdyYSk7IFJhaml2IEFzYXRpIChyYWppdmEpOyBN
aWtlIE1jQnJpZGU7DQo+PiBYdXhpYW9odTsgc2dhbmVzYW5AZXh0cmVtZW5ldHdvcmtzLmNvbQ0K
Pj4gs63LzTogU3RpZyBWZW5hYXM7IHBpbUBpZXRmLm9yZw0KPj4g1vfM4jogUmU6IFtwaW1dIGNh
bGwgZm9yIGFkb3B0aW9uOiBkcmFmdC16aG91LXBpbS12cnJwLTAxDQo+PiANCj4+IEhpLA0KPj4g
DQo+PiBUaGFuayB5b3UgYWxsIGZvciBwcm92aWRpbmcgY29tbWVudHMgYW5kIHRoZSBpbmZvcm1h
dGlvbiBvbg0KPj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQteHUtcGltLWRycHJp
b3JpdHktYXV0by1hZGp1c3RtZW50LTAzLg0KPj4gDQo+PiBJIGp1c3QgcmVhZCB0aHJvdWdoIHRo
ZSBkcmFmdCBwcm9wb3NlZCBieSB4aWFvaHUgYXMgSSB3YXMgbm90IGF3YXJlIG9mDQo+PiB0aGlz
IGRyYWZ0IHVudGlsIHhpYW9odSBraW5kbHkgbWVudGlvbmVkIGluIHRoZSBtYWlsIGxpc3QuIEFm
dGVyDQo+PmNhcmVmdWxseQ0KPj4gY29tcGFyaW5nIHRoZSB0d28gZHJhZnRzLCBsZXQgbWUgdHJ5
IGV4cGxhaW4gdGhlIGRpZmZlcmVuY2VzIGJldHdlZW4NCj4+dGhlbQ0KPj4gKHJlZmVycmVkIGFz
IGRyYWZ0LXh1LWRyLWFkaiBhbmQgZHJhZnQtemhvdS1waW0tdnJycCk6DQo+PiANCj4+IDEuIFRo
ZSBvcmlnaW5hbCBwcm9ibGVtcyB0aGF0IHR3byBkcmFmdHMgdHJ5IHRvIHNvbHZlIG1pZ2h0IGxv
b2sgc2ltaWxhcg0KPj4gYnV0IHRoZXkgYXJlIGFjdHVhbGx5IHF1aXRlIGRpZmZlcmVudCBpbiB0
aGUgZm9sbG93aW5nIHdheToNCj4+IGRyYWZ0LXh1LWRyLWFkaiB0YXJnZXRzIHRoZSBQSU0gRFIg
YXV0by1hZGp1c3RtZW50IGJhc2VkIG9uIHVwc3RyZWFtDQo+PmxpbmsNCj4+IHRyYWNraW5nLCB3
aGlsZSB0aGUgaWRlYSBpbiBkcmFmdC16aG91LXBpbS12cnJwIGlzIHRvIHByb3ZpZGUgYSBjb21w
bGV0ZQ0KPj4gc29sdXRpb24gdG8gZW5hYmxlIG11bHRpY2FzdCB0byBpbnRlcm9wZXJhdGUgd2l0
aCBmaXJzdCBob3AgcmVkdW5kYW5jeQ0KPj4gcHJvdG9jb2wgaW4gcmVzcG9uc2UgdG8gYW55IGlu
dGVyZXN0ZWQgZXZlbnRzOiBNYXN0ZXIgcm91dGVycyBnb2VzIGRvd24sDQo+PiB1cHN0cmVhbSBs
aW5rIHVwL2Rvd24sIGJhbmR3aWR0aCBjaGFuZ2UgYW5kIG90aGVyIGxvZ2ljYWwgb2JqZWN0cyB0
aGF0DQo+PiBWUlJQIGNvdWxkIHRyYWNrLg0KPg0KPkFzIGl0IHNhaWQgaW4gc2VjdGlvbiAyIG9m
IGRyYWZ0LXh1LWRyLWFkaiwNCj4NCj4iICBJbiBmYWN0LCBpZiBWUlJQIGlzIHJ1biBvbiB0aGUg
UElNIHJvdXRlcnMgYW5kIHRoZSBWUlJQIGhhcyBlbmFibGVkDQo+ICAgdGhlIHVwc3RyZWFtIGxp
bmsgdHJhY2tpbmcgbWVjaGFuaXNtLCB0aGUgUElNIERSIGZhaWxvdmVyIG1lY2hhbmlzbQ0KPiAg
IGNvdWxkIGJlIGNvdXBsZWQgd2l0aCB0aGUgVlJSUCBzbyBhcyB0byByZXVzZSB0aGUgdXBzdHJl
YW0gbGluaw0KPiAgIHRyYWNraW5nIG1lY2hhbmlzbSBvZiBWUlJQLiBPbmUgb3B0aW9uIGlzIHRv
IHN5bmNocm9uaXplIHRoZSBQSU0gRFINCj4gICBwcmlvcml0eSB2YWx1ZSB0byB0aGUgVlJSUCBw
cmlvcml0eSB2YWx1ZSBhbHdheXMuIEluIHRoaXMgd2F5LCB0aGUNCj4gICBQSU0gRFIgYW5kIHRo
ZSBWUlJQIG1hc3RlciB3aWxsIGFsd2F5cyBydW4gb24gYW4gaWRlbnRpY2FsIHJvdXRlciBpZg0K
PiAgIHRoZSBWUlJQIFByZWVtcHRfTW9kZSBpcyBzZXQgdG8gVHJ1ZS4gQW5vdGhlciBvcHRpb24g
aXMgdG8gbWFrZSB0aGUNCj4gICBQSU0gRFIgYW5kIHRoZSBWUlJQIG1hc3RlciBydW4gb24gYW4g
aWRlbnRpY2FsIHJvdXRlciBhbnl3YXkgKGkuZS4sDQo+ICAgcmVnYXJkbGVzcyB3aGV0aGVyIG9y
IG5vdCB0aGUgVlJSUCBQcmVlbXB0X01vZGUgaXMgVHJ1ZSkuIFRvIGFjaGlldmUNCj4gICB0aGlz
IGdvYWwsIHRoZSBQSU0gRFIgcHJpb3JpdHkgb2YgdGhlIFZSUlAgbWFzdGVyIHJvdXRlciBTSE9V
TEQNCj4gICBhbHdheXMgYmUgc2V0IHRvIGEgaGlnaGVyIGZpeGVkIHZhbHVlIHRoYW4gdGhhdCBv
ZiB0aGUgVlJSUCBzbGF2ZQ0KPiAgIHJvdXRlciBhdXRvbWF0aWNhbGx5Lg0KPiINCj5JbiBhIHdv
cmQsIHRoZSBQSU0gRFIgYW5kIHRoZSBWUlJQIG1hc3RlciBjb3VsZCBhY3R1YWxseSBydW4gb24g
dGhlIHNhbWUNCj5yb3V0ZXIgbm8gbWF0dGVyIHdoYXRldmVyIGZhY3RvciB0cmlnZ2VycyB0aGUg
VlJSUCBzd2l0Y2hvdmVyLCBhcyBwZXIgdGhlDQo+YWJvdmUgZGVzY3JpcHRpb24uDQo+DQo+PiAy
LiBUaGUgc29sdXRpb24gcHJvcG9zZWQgaW4gZHJhZnQtemhvdS1waW0tdnJycCBpcyBkZXNpZ25l
ZCBhcyBhDQo+PmNvbXBsZXRlDQo+PiBtdWx0aWNhc3QgZmFpbG92ZXIgbWVjaGFuaXNtOiBpbiBh
ZGRpdGlvbiB0byBEUiBwcmlvcml0eSBhZGp1c3RtZW50LCB0aGUNCj4+IG5ldyBkcmFmdCBhZGRy
ZXNzZXMgb3RoZXIgY3JpdGljYWwgcHJvYmxlbXMgaW4gcHJvdmlkaW5nIG11bHRpY2FzdA0KPj4g
cmVkdW5kYW5jeSwgaW5jbHVkaW5nIEFzc2VydCBtZXRyaWMgYWRqdXN0bWVudCwgREYgZWxlY3Rp
b24gZm9yIEJpRGlyDQo+PiBncm91cCBhbmQgdHJhY2tpbmcgbXVsdGlwbGUgVlJSUCBncm91cHMu
DQo+DQo+DQo+PiAzLiBJbiBhZGRpdGlvbiB0byBsYXN0LWhvcCBhbmQgZmlyc3QtaG9wIHNjZW5h
cmlvLCB0aGUgbmV3IGRyYWZ0DQo+PmFkZHJlc3Nlcw0KPj4gIHRyYW5zaXQgbmV0d29yayBzY2Vu
YXJpbyB0byBtYWtlIE1hc3RlciByb3V0ZXIgcHJvY2VzcyBQSU0gSi9QIGZvciB0aGUNCj4+IHZp
cnR1YWwgYWRkcmVzcywgYW5kIGhvdyB0byBtYWludGFpbiBvciByZWJ1aWxkIEovUCBzdGF0ZSB3
aGVuDQo+PnN3aXRjaGluZy4NCj4NCj5Db3VsZCB5b3UgcGxlYXNlIGV4cGxhaW4gdGhlIG1vdGl2
YXRpb24gZm9yIGVuYWJsaW5nIFZSUlAsIHJhdGhlciB0aGFuDQo+SUdQIGluIHRoZSByZWFsIHRy
YW5zaXQgbmV0d29yayBzY2VuYXJpbz8NCj4NCj4+IFRoZSBvbmx5IHNpbWlsYXJpdHkgYmV0d2Vl
biB0aGUgb2xkIGFuZCBuZXcgZHJhZnRzIGlzIHRvIG1ha2UgbWFzdGVyDQo+PiByb3V0ZXIgdGhl
IERSLCB3aGljaCBpcyBvYnZpb3VzIHdheSB0byBtYWtlIGRlc2lyZWQgcm91dGVyIERSLg0KPg0K
PlllcywgdGhpcyBpcyB0aGUgbWFqb3IgbW90aXZhdGlvbiBmb3IgYm90aCBkcmFmdHMgaW4gbXkg
dW5kZXJzdGFuZGluZy4NCj4NCj5CZXN0IHJlZ2FyZHMsDQo+WGlhb2h1DQo+DQo+PiBUaGFua3Ms
DQo+PiBXZWkNCj4+IA0KPj4gDQo+PiANCj4+IA0KPj4gDQo+PiANCj4+IE9uIDUvMjMvMTMgMjow
OCBBTSwgIlByYXNoYW50IEpoaW5ncmFuIChwamhpbmdyYSkiIDxwamhpbmdyYUBjaXNjby5jb20+
DQo+PiB3cm90ZToNCj4+IA0KPj4gPkhpIE1pa2UsDQo+PiA+DQo+PiA+SSBhZ3JlZSB3aXRoIFJh
aml2LCBib3RoIGRyYWZ0cyBhcmUgdHJ5aW5nIHRvIHNvbHZlIHRoZSBzYW1lDQo+PiA+aXNzdWUu
Li4udGhhdCB0b28gaW4gYWxtb3N0IHNpbWlsYXIgd2F5Lg0KPj4gPg0KPj4gPi0NCj4+ID5SZWdh
cmRzLA0KPj4gPlByYXNoYW50IEpoaW5ncmFuDQo+PiA+Tk9TVEcgVE1FIC0gU1AgV2ktRmkNCj4+
ID4NCj4+ID5odHRwOi8vd3d3aW4uY2lzY28uY29tL2lvcy90ZWNoL21vYmlsZS9wcm94eWlwdjYv
DQo+PiA+aHR0cDovL3d3d2luLmNpc2NvLmNvbS9pb3MvdGVjaC9icm9hZGJhbmQNCj4+ID4NCj4+
ID4NCj4+ID4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gPkZyb206IFJhaml2IEFzYXRp
IChyYWppdmEpDQo+PiA+U2VudDogVGh1cnNkYXksIE1heSAyMywgMjAxMyAzOjA2IEFNDQo+PiA+
VG86IE1pa2UgTWNCcmlkZTsgWHV4aWFvaHU7IHNnYW5lc2FuQGV4dHJlbWVuZXR3b3Jrcy5jb207
IFByYXNoYW50DQo+PiA+SmhpbmdyYW4gKHBqaGluZ3JhKTsgV2VpIFpob3UgKHdlaXpobzIpDQo+
PiA+Q2M6IFN0aWcgVmVuYWFzOyBwaW1AaWV0Zi5vcmcNCj4+ID5TdWJqZWN0OiBSRTogW3BpbV0g
Y2FsbCBmb3IgYWRvcHRpb246IGRyYWZ0LXpob3UtcGltLXZycnAtMDENCj4+ID4NCj4+ID5IaSBN
aWtlLA0KPj4gPg0KPj4gPkl0IHNlZW1zIHRoYXQgYm90aCBkcmFmdHMgc2VlbSB0byBzb2x2ZSBu
ZWFybHkgdGhlIHNhbWUgcHJvYmxlbQ0KPj4obXVsdGlwbGUNCj4+ID5yb3V0ZXJzIG9uIHRoZSBt
dWx0aS1hY2Nlc3MgaW50ZXJmYWNlIGFuZCBleGlzdGVuY2Ugb2YgZmlyc3QtaG9wDQo+PiA+cmVk
dW5kYW5jeSBwcm90b2NvbHMgZS5nLiBWUlJQKS4NCj4+ID4NCj4+ID5DaGVlcnMsDQo+PiA+UmFq
aXYNCj4+ID4NCj4+ID4NCj4+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiA+PiBG
cm9tOiBNaWtlIE1jQnJpZGUgW21haWx0bzptbWNicmlkZTdAZ21haWwuY29tXQ0KPj4gPj4gU2Vu
dDogV2VkbmVzZGF5LCBNYXkgMjIsIDIwMTMgMjoxNyBBTQ0KPj4gPj4gVG86IFh1eGlhb2h1OyBz
Z2FuZXNhbkBleHRyZW1lbmV0d29ya3MuY29tOyBSYWppdiBBc2F0aSAocmFqaXZhKTsNCj4+ID4+
IFByYXNoYW50IEpoaW5ncmFuIChwamhpbmdyYSk7IFdlaSBaaG91ICh3ZWl6aG8yKQ0KPj4gPj4g
Q2M6IFN0aWcgVmVuYWFzOyBNaWtlIE1jQnJpZGU7IHBpbUBpZXRmLm9yZw0KPj4gPj4gU3ViamVj
dDogUmU6IFtwaW1dIGNhbGwgZm9yIGFkb3B0aW9uOiBkcmFmdC16aG91LXBpbS12cnJwLTAxDQo+
PiA+Pg0KPj4gPj4gRm9sa3MsDQo+PiA+Pg0KPj4gPj4gV2UgaGF2ZSB0aGlzIG5ldyBkcmFmdC16
aG91LXBpbS12cnJwLTAxIHdoaWNoIHdlIGFyZSBhYm91dCB0byBhZG9wdA0KPj4gPj4gaW50byB0
aGUgcGltIHdnLiBJdCBoYXMgYmVlbiBicm91Z2h0IHRvIHRoZSBXR3MgYXR0ZW50aW9uIHRoYXQg
dGhlcmUNCj4+ID4+IGlzIGEgb2xkZXIgZHJhZnQgKGRyYWZ0LXh1LXBpbS1kcnByaW9yaXR5LWF1
dG8tYWRqdXN0bWVudC0wMykgd2hpY2gNCj4+ID4+IG1heSBoYXZlIHNvbWUgb3ZlcmxhcCB3aXRo
IHRoZSBuZXcgb25lLiBUaGF0IG9sZGVyIGRyYWZ0IGRvZXMgY29udGFpbg0KPj4gPj4gaW5mb3Jt
YXRpb24gYWJvdXQgVlJSUCBhd2FyZSBQSU0gd2hpY2ggaXMgYXR0cmlidXRlZCB0byBTdGlnIGlu
IHRoZQ0KPj4gPj4gYWNrbm93bGVkZ2VtZW50cy4gSWYgdGhlIGZpdmUgb2YgeW91IGF1dGhvcnMg
ZmVlbCB0aGF0IHRoZXJlIGlzIHNvbWUNCj4+ID4+IHZhbGlkaXR5IHRoYXQgdGhlIG9sZGVyIGRy
YWZ0IGNvbnRhaW5zIHNvbWUgaW5mb3JtYXRpb24gYmVpbmcgdXNlZCBpbg0KPj4gPj4gdGhlIG5l
dyBkcmFmdCwgeW91IG1heSB3YW50IHRvIGFja25vd2xlZGdlIHRoYXQgaW4gdGhlIHJlZmVyZW5j
ZXMgb3INCj4+ID4+IGFja25vd2xlZGdlbWVudHMuIEl0IGFwcGVhcnMgdGhlIGRyYWZ0cyBhcmUg
ZGlzc2ltaWxhciBlbm91Z2ggdG8gbm90DQo+PiA+PiBiZSBtZXJnZWQgYnV0IEkgbWF5IGJlIHdy
b25nLiBQbGVhc2Ugc2hhcmUgeW91ciBvcGluaW9ucyBvbiB0aGlzIHNvDQo+PndlDQo+PiA+PiBj
YW4gZXN0YWJsaXNoIGNvbnNlbnN1cyB3aXRoaW4gdGhlIGdyb3VwIGFuZCBtb3ZlIHRoZSBkb2N1
bWVudCBhbG9uZy4NCj4+ID4+DQo+PiA+PiBJZiB0aGUgYnJvYWRlciBXRyBwYXJ0aWNpcGFudHMg
aGF2ZSBhbiBvcGluaW9uIG9uIHRoaXMgcGxlYXNlIHNwZWFrDQo+PnVwLg0KPj4gPj4NCj4+ID4+
IHRoYW5rcywNCj4+ID4+IG1pa2UNCj4+ID4+DQo+PiA+PiBPbiBUaHUsIE1heSA5LCAyMDEzIGF0
IDc6MzIgUE0sIFh1eGlhb2h1IDx4dXhpYW9odUBodWF3ZWkuY29tPiB3cm90ZToNCj4+ID4+ID4g
SGkgYWxsLA0KPj4gPj4gPg0KPj4gPj4gPiBUaGlzIGRyYWZ0IHJlbWluZHMgbWUgdGhhdCB0aGVy
ZSBoYXMgYmVlbiBhIGRyYWZ0DQo+PiA+PiANCj4+KGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LXh1LXBpbS1kcnByaW9yaXR5LWF1dG8tYWRqdXN0bWVudC0wMw0KPj4gPj4gKSB0aHJl
ZSB5ZWFycyBiZWZvcmUgd2hpY2ggdXNlcyBhbG1vc3QgdGhlIHNhbWUgdGVjaG5vbG9neSB0byBz
YXZlDQo+PiA+PiBhbG1vc3QgdGhlIHNhbWUgcHJvYmxlbS4NCj4+ID4+ID4NCj4+ID4+ID4gVGhl
IGZvbGxvd2luZyBpcyBxdW90ZWQgZnJvbSB0aGUgYWJvdmUgZHJhZnQ6DQo+PiA+PiA+DQo+PiA+
PiA+ICAgICJJbiBmYWN0LCBpZiBWUlJQIGlzIHJ1biBvbiB0aGUgUElNIHJvdXRlcnMgYW5kIHRo
ZSBWUlJQIGhhcw0KPj4gPj5lbmFibGVkDQo+PiA+PiA+ICAgIHRoZSB1cHN0cmVhbSBsaW5rIHRy
YWNraW5nIG1lY2hhbmlzbSwgdGhlIFBJTSBEUiBmYWlsb3Zlcg0KPj4gbWVjaGFuaXNtDQo+PiA+
PiA+ICAgIGNvdWxkIGJlIGNvdXBsZWQgd2l0aCB0aGUgVlJSUCBzbyBhcyB0byByZXVzZSB0aGUg
dXBzdHJlYW0gbGluaw0KPj4gPj4gPiAgICB0cmFja2luZyBtZWNoYW5pc20gb2YgVlJSUC4gT25l
IG9wdGlvbiBpcyB0byBzeW5jaHJvbml6ZSB0aGUNCj4+UElNIERSDQo+PiA+PiA+ICAgIHByaW9y
aXR5IHZhbHVlIHRvIHRoZSBWUlJQIHByaW9yaXR5IHZhbHVlIGFsd2F5cy4gSW4gdGhpcyB3YXks
DQo+PnRoZQ0KPj4gPj4gPiAgICBQSU0gRFIgYW5kIHRoZSBWUlJQIG1hc3RlciB3aWxsIGFsd2F5
cyBydW4gb24gYW4gaWRlbnRpY2FsDQo+PnJvdXRlcg0KPj4gPj5pZg0KPj4gPj4gPiAgICB0aGUg
VlJSUCBQcmVlbXB0X01vZGUgaXMgc2V0IHRvIFRydWUuIEFub3RoZXIgb3B0aW9uIGlzIHRvIG1h
a2UNCj4+dGhlDQo+PiA+PiA+ICAgIFBJTSBEUiBhbmQgdGhlIFZSUlAgbWFzdGVyIHJ1biBvbiBh
biBpZGVudGljYWwgcm91dGVyIGFueXdheQ0KPj4oaS5lLiwNCj4+ID4+ID4gICAgcmVnYXJkbGVz
cyB3aGV0aGVyIG9yIG5vdCB0aGUgVlJSUCBQcmVlbXB0X01vZGUgaXMgVHJ1ZSkuIFRvDQo+PiA+
PmFjaGlldmUNCj4+ID4+ID4gICAgdGhpcyBnb2FsLCB0aGUgUElNIERSIHByaW9yaXR5IG9mIHRo
ZSBWUlJQIG1hc3RlciByb3V0ZXIgU0hPVUxEDQo+PiA+PiA+ICAgIGFsd2F5cyBiZSBzZXQgdG8g
YSBoaWdoZXIgZml4ZWQgdmFsdWUgdGhhbiB0aGF0IG9mIHRoZSBWUlJQDQo+PnNsYXZlDQo+PiA+
PiA+ICAgIHJvdXRlciBhdXRvbWF0aWNhbGx5LiINCj4+ID4+ID4NCj4+ID4+ID4gQmVzdCByZWdh
cmRzLA0KPj4gPj4gPiBYaWFvaHUNCj4+ID4+ID4NCj4+ID4+ID4+IC0tLS0t08q8/tStvP4tLS0t
LQ0KPj4gPj4gPj4gt6K8/sjLOiBwaW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnBpbS1ib3Vu
Y2VzQGlldGYub3JnXSC0+rHtDQo+PiA+PiBNaWtlDQo+PiA+PiA+PiBNY0JyaWRlDQo+PiA+PiA+
PiC3osvNyrG85DogMjAxM8TqNdTCMTDI1SAzOjQ4DQo+PiA+PiA+PiDK1bz+yMs6IHBpbUBpZXRm
Lm9yZw0KPj4gPj4gPj4g1vfM4jogW3BpbV0gY2FsbCBmb3IgYWRvcHRpb246IGRyYWZ0LXpob3Ut
cGltLXZycnAtMDENCj4+ID4+ID4+DQo+PiA+PiA+PiBkcmFmdC16aG91LXBpbS12cnJwLTAxIHdh
cyBwcmVzZW50ZWQgaW4gb3VyIG1vc3QgcmVjZW50IHBpbQ0KPj5tZWV0aW5nDQo+PiA+PiA+PiBp
biBPcmxhbmRvLiA0IHBlb3BsZSB3ZXJlIGluIGZhdm9yIG9mIGFkb3B0aW5nIHRoZSBkcmFmdC4g
WmVybw0KPj4gPj5hZ2FpbnN0Lg0KPj4gPj4gPj4gUGxlYXNlIHJlYWQgdGhlIGRyYWZ0IChpdHMg
c2hvcnQpIGFuZCBwcm92aWRlIGFuIG9waW5pb24gZWl0aGVyDQo+PndheQ0KPj4gPj4gPj4gYnkg
dGhlIGVuZCBvZiBuZXh0IEZyaWRheSB0aGUgMTd0aC4NCj4+ID4+ID4+DQo+PiA+PiA+PiBodHRw
Oi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LXpob3UtcGltLXZycnAtMDEudHh0DQo+PiA+PiA+Pg0K
Pj4gPj4gPj4gdGhhbmtzLA0KPj4gPj4gPj4gbWlrZQ0KPj4gPj4gPj4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+ID4+ID4+IHBpbSBtYWlsaW5nIGxp
c3QNCj4+ID4+ID4+IHBpbUBpZXRmLm9yZw0KPj4gPj4gPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9waW0NCj4NCg0K

From bharat_joshi@infosys.com  Tue May 28 20:38:31 2013
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4983421F8756 for <pim@ietfa.amsl.com>; Tue, 28 May 2013 20:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id riJj3HKvN5dy for <pim@ietfa.amsl.com>; Tue, 28 May 2013 20:38:23 -0700 (PDT)
Received: from KECGATE08.infosys.com (kecgate08.infosys.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id D53B521F8681 for <pim@ietf.org>; Tue, 28 May 2013 20:38:22 -0700 (PDT)
X-TM-IMSS-Message-ID: <044e62ff0000b937@infosys.com>
Received: from blrkechub03.ad.infosys.com ([10.66.236.43]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 044e62ff0000b937 ; Wed, 29 May 2013 09:15:15 +0530
Received: from BLRKECHUB06.ad.infosys.com (10.66.236.116) by blrkechub03.ad.infosys.com (10.66.236.43) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 29 May 2013 09:07:43 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by BLRKECHUB06.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Wed, 29 May 2013 09:07:42 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Stig Venaas <stig@venaas.com>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] Reminder: pim WGLC for draft-ietf-pim-rfc4601-update-survey-report-00
Thread-Index: AQHOW9EKVz9Yr4LHvEqUs+QMIiLlI5kbgaD8
Date: Wed, 29 May 2013 03:37:42 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED32E5436B@BLRKECMBX13.ad.infosys.com>
References: <519BA747.1030201@venaas.com>,<51A4F72C.9040507@venaas.com>
In-Reply-To: <51A4F72C.9040507@venaas.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [pim] Reminder: pim WGLC for	draft-ietf-pim-rfc4601-update-survey-report-00
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 29 May 2013 03:38:31 -0000

I think the document is ready for publication. However I have few edits t=
o suggest:

1. In "and a detailed summary of the responses", detailed and summary tog=
ether does not look right.

2. "Join Suppression" -> "Join suppression". This is how it is used in RF=
C 4601.

Thanks,
Bharat
________________________________________
From: pim-bounces@ietf.org [pim-bounces@ietf.org] on behalf of Stig Venaa=
s [stig@venaas.com]
Sent: Tuesday, May 28, 2013 11:57 PM
To: pim@ietf.org
Subject: [pim] Reminder: pim WGLC for   draft-ietf-pim-rfc4601-update-sur=
vey-report-00

This last call ends Sunday, we need more people to review this.

Stig

On 5/21/2013 9:56 AM, Stig Venaas wrote:
> Hi
>
> We, the chairs, want to speed up the process of updating RFC 4601
> and as a next step we want to make sure that you, the working group,
> are happy with the implementation report. Once the group is happy, we
> want to get the report published, and then finalize the updates to
> 4601 based on that.
>
> The report results have been presented to the group. There were some
> comments in the adoption call, and the adopted version took them into
> account. The draft is available at
> http://tools.ietf.org/html/draft-ietf-pim-rfc4601-update-survey-report-=
00
>
> With this email we're starting a working group last call, ending
> Sunday June 2nd. This is important work and we need your review. It
> is the bases for updating one of our core RFCs, please read through
> the report and tell us whether it is ready to be published.
>
> Stig
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim

_______________________________________________
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 mmcbride7@gmail.com  Fri May 31 00:06:53 2013
Return-Path: <mmcbride7@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6249321F8624 for <pim@ietfa.amsl.com>; Fri, 31 May 2013 00:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.189
X-Spam-Level: 
X-Spam-Status: No, score=0.189 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id miTiU7sL5Wte for <pim@ietfa.amsl.com>; Fri, 31 May 2013 00:06:48 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEB421F9344 for <pim@ietf.org>; Fri, 31 May 2013 00:06:45 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id jt11so1716133pbb.38 for <pim@ietf.org>; Fri, 31 May 2013 00:06:45 -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:content-transfer-encoding; bh=e43j27rtpFjHlTFpZ4tVtcsbqpBI83dRcdjCn/5NED4=; b=Di8ahn7PxgK0mG9y+EpuOnCV9cOm8F1GcNH1IeW5W1ldCVvI8hWpIyoejBXphwCARE dxn+NAKKnsS7uG6cOUtKez02hJz5MuqtTxh9dXUka4DS1eSUfwscHdqyr7b013TJlJl9 nbi1tUgWLp2lHKer99epE/a2Hi1pVxccWokKKrmY3XSpfwEKq4AvZHcz1HUzu8dwmss+ UpugQ4LE/NAyJjNSCNczuUikoO5JjHgyIyysQ/5z1fVRPfBm5ywZSSFkEk5UlkrEgoLp DwUWES1AUL5ZQhJ7HgpUhLpv1gZmI1G/626vsxOsXXSDrvOjGCYoji/jbU5gyx/nGRYl an0A==
MIME-Version: 1.0
X-Received: by 10.66.122.97 with SMTP id lr1mr12023675pab.147.1369984004897; Fri, 31 May 2013 00:06:44 -0700 (PDT)
Received: by 10.68.59.232 with HTTP; Fri, 31 May 2013 00:06:44 -0700 (PDT)
In-Reply-To: <F567B77E0728694BB6716DB3C9000B6B12ABC487@xmb-rcd-x14.cisco.com>
References: <CAL3FGfwaXhsfRoJXo17LipzGNvUH0jL2sQdcrmMqzBa0ZB16og@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07F669D4@NKGEML512-MBS.china.huawei.com> <CAL3FGfy2WdAmtnUO97nx0TYMeMqStkUmJfa42VDu=6MOykbzwQ@mail.gmail.com> <B14A62A57AB87D45BB6DD7D9D2B78F0B116B0DB0@xmb-rcd-x06.cisco.com> <F567B77E0728694BB6716DB3C9000B6B12ABC487@xmb-rcd-x14.cisco.com>
Date: Fri, 31 May 2013 00:06:44 -0700
Message-ID: <CAL3FGfyVgze+tVyErjcKaME6esNKRmEYqcobZGpHxBnsTewibg@mail.gmail.com>
From: Mike McBride <mmcbride7@gmail.com>
To: "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable
Cc: "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 31 May 2013 07:06:53 -0000

Thank you for the responses.

Some feel the two drafts are completely unrelated while others feel
they are completely related. In either case, are you, who feel they
are related, saying you oppose the adoption of draft-zhou-pim-vrrp-01?
We can infer that is the case but I haven't heard explicitly stated
opposition to adoption. We now have several choices for
draft-zhou-pim-vrrp, let me try boiling it down to 3:

1. adopt draft-zhou-pim-vrrp-01 as is
2. adopt draft-zhou-pim-vrrp-01 only after
draft-xu-pim-drpriority-auto-adjustment is referenced.
3. merge the drafts

In either case the authors should revive the expired
draft-xu-pim-drpriority-auto-adjustment-03 for consideration within
the wg irregardless of vrrp-01 adoption outcome.

What say ye?

mike

On Thu, May 23, 2013 at 2:08 AM, Prashant Jhingran (pjhingra)
<pjhingra@cisco.com> wrote:
> Hi Mike,
>
> I agree with Rajiv, both drafts are trying to solve the same issue....tha=
t too in almost similar way.
>
> -
> Regards,
> Prashant Jhingran
> NOSTG TME - SP Wi-Fi
>
> http://wwwin.cisco.com/ios/tech/mobile/proxyipv6/
> http://wwwin.cisco.com/ios/tech/broadband
>
>
> -----Original Message-----
> From: Rajiv Asati (rajiva)
> Sent: Thursday, May 23, 2013 3:06 AM
> To: Mike McBride; Xuxiaohu; sganesan@extremenetworks.com; Prashant Jhingr=
an (pjhingra); Wei Zhou (weizho2)
> Cc: Stig Venaas; pim@ietf.org
> Subject: RE: [pim] call for adoption: draft-zhou-pim-vrrp-01
>
> Hi Mike,
>
> It seems that both drafts seem to solve nearly the same problem (multiple=
 routers on the multi-access interface and existence of first-hop redundanc=
y protocols e.g. VRRP).
>
> Cheers,
> Rajiv
>
>
>> -----Original Message-----
>> From: Mike McBride [mailto:mmcbride7@gmail.com]
>> Sent: Wednesday, May 22, 2013 2:17 AM
>> To: Xuxiaohu; sganesan@extremenetworks.com; Rajiv Asati (rajiva);
>> Prashant Jhingran (pjhingra); Wei Zhou (weizho2)
>> Cc: Stig Venaas; Mike McBride; pim@ietf.org
>> Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
>>
>> Folks,
>>
>> We have this new draft-zhou-pim-vrrp-01 which we are about to adopt
>> into the pim wg. It has been brought to the WGs attention that there
>> is a older draft (draft-xu-pim-drpriority-auto-adjustment-03) which
>> may have some overlap with the new one. That older draft does contain
>> information about VRRP aware PIM which is attributed to Stig in the
>> acknowledgements. If the five of you authors feel that there is some
>> validity that the older draft contains some information being used in
>> the new draft, you may want to acknowledge that in the references or
>> acknowledgements. It appears the drafts are dissimilar enough to not
>> be merged but I may be wrong. Please share your opinions on this so we
>> can establish consensus within the group and move the document along.
>>
>> If the broader WG participants have an opinion on this please speak up.
>>
>> thanks,
>> mike
>>
>> On Thu, May 9, 2013 at 7:32 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>> > Hi all,
>> >
>> > This draft reminds me that there has been a draft
>> (http://tools.ietf.org/html/draft-xu-pim-drpriority-auto-adjustment-03
>> ) three years before which uses almost the same technology to save
>> almost the same problem.
>> >
>> > The following is quoted from the above draft:
>> >
>> >    "In fact, if VRRP is run on the PIM routers and the VRRP has enable=
d
>> >    the upstream link tracking mechanism, the PIM DR failover mechanism
>> >    could be coupled with the VRRP so as to reuse the upstream link
>> >    tracking mechanism of VRRP. One option is to synchronize the PIM DR
>> >    priority value to the VRRP priority value always. In this way, the
>> >    PIM DR and the VRRP master will always run on an identical router i=
f
>> >    the VRRP Preempt_Mode is set to True. Another option is to make the
>> >    PIM DR and the VRRP master run on an identical router anyway (i.e.,
>> >    regardless whether or not the VRRP Preempt_Mode is True). To achiev=
e
>> >    this goal, the PIM DR priority of the VRRP master router SHOULD
>> >    always be set to a higher fixed value than that of the VRRP slave
>> >    router automatically."
>> >
>> > Best regards,
>> > Xiaohu
>> >
>> >> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
>> >> =B7=A2=BC=FE=C8=CB: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org=
] =B4=FA=B1=ED
>> Mike
>> >> McBride
>> >> =B7=A2=CB=CD=CA=B1=BC=E4: 2013=C4=EA5=D4=C210=C8=D5 3:48
>> >> =CA=D5=BC=FE=C8=CB: pim@ietf.org
>> >> =D6=F7=CC=E2: [pim] call for adoption: draft-zhou-pim-vrrp-01
>> >>
>> >> draft-zhou-pim-vrrp-01 was presented in our most recent pim meeting
>> >> in Orlando. 4 people were in favor of adopting the draft. Zero agains=
t.
>> >> Please read the draft (its short) and provide an opinion either way
>> >> by the end of next Friday the 17th.
>> >>
>> >> http://www.ietf.org/id/draft-zhou-pim-vrrp-01.txt
>> >>
>> >> thanks,
>> >> mike
>> >> _______________________________________________
>> >> pim mailing list
>> >> pim@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/pim

From stig@venaas.com  Fri May 31 09:58:01 2013
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2CF21F852D for <pim@ietfa.amsl.com>; Fri, 31 May 2013 09:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8U4xqDAFN8Be for <pim@ietfa.amsl.com>; Fri, 31 May 2013 09:58:00 -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 A235E21F8528 for <pim@ietf.org>; Fri, 31 May 2013 09:57:57 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 002CE82D3; Fri, 31 May 2013 18:57:55 +0200 (CEST)
Message-ID: <51A8D692.9000301@venaas.com>
Date: Fri, 31 May 2013 09:57:54 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: pim@ietf.org
References: <519BA747.1030201@venaas.com> <51A4F72C.9040507@venaas.com>
In-Reply-To: <51A4F72C.9040507@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "draft-zzp-pim-rfc4601-update-survey-report@tools.ietf.org" <draft-zzp-pim-rfc4601-update-survey-report@tools.ietf.org>
Subject: Re: [pim] Reminder: pim WGLC for draft-ietf-pim-rfc4601-update-survey-report-00
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 31 May 2013 16:58:01 -0000

On 5/28/2013 11:27 AM, Stig Venaas wrote:
> This last call ends Sunday, we need more people to review this.

Here are my comments. Hope more people will respond.

In 1.1 it says:

    2006.  Considering its multiple independent implementations developed
    and sufficient successful operational experience gained, the IETF has
    decided to advance the PIM-SM protocol to Internet Standard.

Maybe this is OK, but the IETF hasn't decided to advance PIM-SM yet.
Perhaps just say that the PIM WG wants to advance PIM-SM to Internet
Standard, and that the survey and this document is part of that work.

At the end of 1.2 we have:

    Optional features that do not meet the aforesaid criteria have been
    identified by the PIM Working Group and will be removed.  This
    document intends to provide supporting documentation to advance the
    Protocol Independent Multicast - Sparse Mode (PIM-SM)
    protocol from IETF Proposed Standard to Standard.
                                           ^^^^^^^^^^

Standard should be Internet Standard.

In 2.1 it says:

    22nd Oct 2012.  The responses are kept strictly confidential and
    only combined results are published here.  The raw questionnaire is
    shown in Appendix A, and a detailed summary of the responses is
    included in the following section.

Worth noting that while the details were kept confidential (are they?),
the responders chose whether they wanted the affiliations to be
confidential. It seems a bit strange saying it is strictly confidential,
and then listing names of responders.

Once these issues are taken care of I believe the document is ready to
be sent on to the IESG.

Stig


> Stig
>
> On 5/21/2013 9:56 AM, Stig Venaas wrote:
>> Hi
>>
>> We, the chairs, want to speed up the process of updating RFC 4601
>> and as a next step we want to make sure that you, the working group,
>> are happy with the implementation report. Once the group is happy, we
>> want to get the report published, and then finalize the updates to
>> 4601 based on that.
>>
>> The report results have been presented to the group. There were some
>> comments in the adoption call, and the adopted version took them into
>> account. The draft is available at
>> http://tools.ietf.org/html/draft-ietf-pim-rfc4601-update-survey-report-00
>>
>> With this email we're starting a working group last call, ending
>> Sunday June 2nd. This is important work and we need your review. It
>> is the bases for updating one of our core RFCs, please read through
>> the report and tell us whether it is ready to be published.
>>
>> Stig
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From weizho2@cisco.com  Fri May 31 11:55:43 2013
Return-Path: <weizho2@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E5FB21F93BA for <pim@ietfa.amsl.com>; Fri, 31 May 2013 11:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.057
X-Spam-Level: 
X-Spam-Status: No, score=-6.057 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L1cR4r3Gdcpi for <pim@ietfa.amsl.com>; Fri, 31 May 2013 11:55:38 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 1B88A21F938E for <pim@ietf.org>; Fri, 31 May 2013 11:55:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8068; q=dns/txt; s=iport; t=1370026537; x=1371236137; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=0oX8bF4kBccacQ5eDKQWvEOLAYwyRunN7g1chyD20cY=; b=am6N7oBSko7OuQR39fw/7b//6ILgZIBOJmWlXfiyzaEflrXUrA3u8HXv EWHY0qjzdv7MRsbmmcMnDCuyUDP+hy05yw4tCbhzMfzxcb6nSJNSqzHGe aMiV4dKTdD+44Z2VQZfWRHL2Ymg0pHQuO7OFdANRMfMRsJflyCv6QTYQC s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlcFALDxqFGtJXHB/2dsb2JhbABagwkwgzy7Mg12FnSCIwEBAQQBAQEaFzoLDAYBBgIRBAEBAQQGHQUEHwYLFAkIAgQBDQUIAYdyAw8MjGubNgiIeA2IS4EiiyaCJgIWGwcGgjk3YQOVWIMPinSFI4MPgic
X-IronPort-AV: E=Sophos;i="4.87,780,1363132800"; d="scan'208";a="217347164"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 31 May 2013 18:55:36 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4VIta2s012431 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 May 2013 18:55:36 GMT
Received: from xmb-rcd-x05.cisco.com ([169.254.15.201]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Fri, 31 May 2013 13:55:35 -0500
From: "Wei Zhou (weizho2)" <weizho2@cisco.com>
To: Mike McBride <mmcbride7@gmail.com>, "Prashant Jhingran (pjhingra)" <pjhingra@cisco.com>
Thread-Topic: [pim] call for adoption: draft-zhou-pim-vrrp-01
Thread-Index: AQHOVrP+uggkeQnYAUax3C6a4z91JZkSDz2AgADBXYCADHCgAIAAULMA
Date: Fri, 31 May 2013 18:55:35 +0000
Message-ID: <23EF39780ADBDE42806FAEE7B8578690183E5E6E@xmb-rcd-x05.cisco.com>
In-Reply-To: <CAL3FGfyVgze+tVyErjcKaME6esNKRmEYqcobZGpHxBnsTewibg@mail.gmail.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.209.193]
Content-Type: text/plain; charset="gb2312"
Content-ID: <81EB4BF6AA273F41AAD0E3AC9641C808@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "sganesan@extremenetworks.com" <sganesan@extremenetworks.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
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, 31 May 2013 18:55:43 -0000

SGksDQoNClRoYW5rIHlvdSBhbGwgZm9yIHRoZSBjb21tZW50cyBhbmQgdGhvdWdodHMuIEkgYmVs
aWV2ZSB0aGF0IHRoZSBvbGQgZHJhZnQNCmlzIGFib3V0IHVwc3RyZWFtIGxpbmsgZmFpbHVyZXMs
IHdoaWNoIGlzIG5vdCB3aGF0IHRoZSBuZXcgZHJhZnQgaXMgYWJvdXQuDQpUaGUgbmV3IGRyYWZ0
IGlzIGFib3V0IGhvdyB0byBzdXBwb3J0IFBJTSBhbmQgVlJSUCBpbiBnZW5lcmFsIGluc3RlYWQg
b2YNCmZvY3VzaW5nIG9uIHRoZSBvYmplY3QgYmVpbmcgdHJhY2tlZC4NCg0KSWYgdGhlIFdHIHRo
aW5rIHRoZSB1cHN0cmVhbSBsaW5rIGZhaWx1cmUgc2NlbmFyaW8gc2hvdWxkIGJlIGRpc2N1c3Nl
ZCBpbg0KZGV0YWlsIGluIHRoZSBuZXcgZHJhZnQsIHRoZW4gSSdtIGNvbXBsZXRlbHkgZmluZSB3
aXRoIG1lcmdpbmcuIE1vcmVvdmVyLA0KaWYgdGhlIG5ldyBkcmFmdCBpcyBhZG9wdGVkIGluIGl0
cyBjdXJyZW50IHNoYXBlLCB0aGVuIHRoZSBXRyBjYW4gYWx3YXlzDQpkZWNpZGUgdG8gaW5jbHVk
ZSB0aGUgdXBzdHJlYW0gbGluayBmYWlsdXJlIHNjZW5hcmlvIGxhdGVyLg0KDQpUaGFua3MsDQpX
ZWkNCg0KDQoNCg0KDQpPbiA1LzMxLzEzIDEyOjA2IEFNLCAiTWlrZSBNY0JyaWRlIiA8bW1jYnJp
ZGU3QGdtYWlsLmNvbT4gd3JvdGU6DQoNCj5UaGFuayB5b3UgZm9yIHRoZSByZXNwb25zZXMuDQo+
DQo+U29tZSBmZWVsIHRoZSB0d28gZHJhZnRzIGFyZSBjb21wbGV0ZWx5IHVucmVsYXRlZCB3aGls
ZSBvdGhlcnMgZmVlbA0KPnRoZXkgYXJlIGNvbXBsZXRlbHkgcmVsYXRlZC4gSW4gZWl0aGVyIGNh
c2UsIGFyZSB5b3UsIHdobyBmZWVsIHRoZXkNCj5hcmUgcmVsYXRlZCwgc2F5aW5nIHlvdSBvcHBv
c2UgdGhlIGFkb3B0aW9uIG9mIGRyYWZ0LXpob3UtcGltLXZycnAtMDE/DQo+V2UgY2FuIGluZmVy
IHRoYXQgaXMgdGhlIGNhc2UgYnV0IEkgaGF2ZW4ndCBoZWFyZCBleHBsaWNpdGx5IHN0YXRlZA0K
Pm9wcG9zaXRpb24gdG8gYWRvcHRpb24uIFdlIG5vdyBoYXZlIHNldmVyYWwgY2hvaWNlcyBmb3IN
Cj5kcmFmdC16aG91LXBpbS12cnJwLCBsZXQgbWUgdHJ5IGJvaWxpbmcgaXQgZG93biB0byAzOg0K
Pg0KPjEuIGFkb3B0IGRyYWZ0LXpob3UtcGltLXZycnAtMDEgYXMgaXMNCj4yLiBhZG9wdCBkcmFm
dC16aG91LXBpbS12cnJwLTAxIG9ubHkgYWZ0ZXINCj5kcmFmdC14dS1waW0tZHJwcmlvcml0eS1h
dXRvLWFkanVzdG1lbnQgaXMgcmVmZXJlbmNlZC4NCj4zLiBtZXJnZSB0aGUgZHJhZnRzDQo+DQo+
SW4gZWl0aGVyIGNhc2UgdGhlIGF1dGhvcnMgc2hvdWxkIHJldml2ZSB0aGUgZXhwaXJlZA0KPmRy
YWZ0LXh1LXBpbS1kcnByaW9yaXR5LWF1dG8tYWRqdXN0bWVudC0wMyBmb3IgY29uc2lkZXJhdGlv
biB3aXRoaW4NCj50aGUgd2cgaXJyZWdhcmRsZXNzIG9mIHZycnAtMDEgYWRvcHRpb24gb3V0Y29t
ZS4NCj4NCj5XaGF0IHNheSB5ZT8NCj4NCj5taWtlDQo+DQo+T24gVGh1LCBNYXkgMjMsIDIwMTMg
YXQgMjowOCBBTSwgUHJhc2hhbnQgSmhpbmdyYW4gKHBqaGluZ3JhKQ0KPjxwamhpbmdyYUBjaXNj
by5jb20+IHdyb3RlOg0KPj4gSGkgTWlrZSwNCj4+DQo+PiBJIGFncmVlIHdpdGggUmFqaXYsIGJv
dGggZHJhZnRzIGFyZSB0cnlpbmcgdG8gc29sdmUgdGhlIHNhbWUNCj4+aXNzdWUuLi4udGhhdCB0
b28gaW4gYWxtb3N0IHNpbWlsYXIgd2F5Lg0KPj4NCj4+IC0NCj4+IFJlZ2FyZHMsDQo+PiBQcmFz
aGFudCBKaGluZ3Jhbg0KPj4gTk9TVEcgVE1FIC0gU1AgV2ktRmkNCj4+DQo+PiBodHRwOi8vd3d3
aW4uY2lzY28uY29tL2lvcy90ZWNoL21vYmlsZS9wcm94eWlwdjYvDQo+PiBodHRwOi8vd3d3aW4u
Y2lzY28uY29tL2lvcy90ZWNoL2Jyb2FkYmFuZA0KPj4NCj4+DQo+PiAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPj4gRnJvbTogUmFqaXYgQXNhdGkgKHJhaml2YSkNCj4+IFNlbnQ6IFRodXJz
ZGF5LCBNYXkgMjMsIDIwMTMgMzowNiBBTQ0KPj4gVG86IE1pa2UgTWNCcmlkZTsgWHV4aWFvaHU7
IHNnYW5lc2FuQGV4dHJlbWVuZXR3b3Jrcy5jb207IFByYXNoYW50DQo+PkpoaW5ncmFuIChwamhp
bmdyYSk7IFdlaSBaaG91ICh3ZWl6aG8yKQ0KPj4gQ2M6IFN0aWcgVmVuYWFzOyBwaW1AaWV0Zi5v
cmcNCj4+IFN1YmplY3Q6IFJFOiBbcGltXSBjYWxsIGZvciBhZG9wdGlvbjogZHJhZnQtemhvdS1w
aW0tdnJycC0wMQ0KPj4NCj4+IEhpIE1pa2UsDQo+Pg0KPj4gSXQgc2VlbXMgdGhhdCBib3RoIGRy
YWZ0cyBzZWVtIHRvIHNvbHZlIG5lYXJseSB0aGUgc2FtZSBwcm9ibGVtDQo+PihtdWx0aXBsZSBy
b3V0ZXJzIG9uIHRoZSBtdWx0aS1hY2Nlc3MgaW50ZXJmYWNlIGFuZCBleGlzdGVuY2Ugb2YNCj4+
Zmlyc3QtaG9wIHJlZHVuZGFuY3kgcHJvdG9jb2xzIGUuZy4gVlJSUCkuDQo+Pg0KPj4gQ2hlZXJz
LA0KPj4gUmFqaXYNCj4+DQo+Pg0KPj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4g
RnJvbTogTWlrZSBNY0JyaWRlIFttYWlsdG86bW1jYnJpZGU3QGdtYWlsLmNvbV0NCj4+PiBTZW50
OiBXZWRuZXNkYXksIE1heSAyMiwgMjAxMyAyOjE3IEFNDQo+Pj4gVG86IFh1eGlhb2h1OyBzZ2Fu
ZXNhbkBleHRyZW1lbmV0d29ya3MuY29tOyBSYWppdiBBc2F0aSAocmFqaXZhKTsNCj4+PiBQcmFz
aGFudCBKaGluZ3JhbiAocGpoaW5ncmEpOyBXZWkgWmhvdSAod2VpemhvMikNCj4+PiBDYzogU3Rp
ZyBWZW5hYXM7IE1pa2UgTWNCcmlkZTsgcGltQGlldGYub3JnDQo+Pj4gU3ViamVjdDogUmU6IFtw
aW1dIGNhbGwgZm9yIGFkb3B0aW9uOiBkcmFmdC16aG91LXBpbS12cnJwLTAxDQo+Pj4NCj4+PiBG
b2xrcywNCj4+Pg0KPj4+IFdlIGhhdmUgdGhpcyBuZXcgZHJhZnQtemhvdS1waW0tdnJycC0wMSB3
aGljaCB3ZSBhcmUgYWJvdXQgdG8gYWRvcHQNCj4+PiBpbnRvIHRoZSBwaW0gd2cuIEl0IGhhcyBi
ZWVuIGJyb3VnaHQgdG8gdGhlIFdHcyBhdHRlbnRpb24gdGhhdCB0aGVyZQ0KPj4+IGlzIGEgb2xk
ZXIgZHJhZnQgKGRyYWZ0LXh1LXBpbS1kcnByaW9yaXR5LWF1dG8tYWRqdXN0bWVudC0wMykgd2hp
Y2gNCj4+PiBtYXkgaGF2ZSBzb21lIG92ZXJsYXAgd2l0aCB0aGUgbmV3IG9uZS4gVGhhdCBvbGRl
ciBkcmFmdCBkb2VzIGNvbnRhaW4NCj4+PiBpbmZvcm1hdGlvbiBhYm91dCBWUlJQIGF3YXJlIFBJ
TSB3aGljaCBpcyBhdHRyaWJ1dGVkIHRvIFN0aWcgaW4gdGhlDQo+Pj4gYWNrbm93bGVkZ2VtZW50
cy4gSWYgdGhlIGZpdmUgb2YgeW91IGF1dGhvcnMgZmVlbCB0aGF0IHRoZXJlIGlzIHNvbWUNCj4+
PiB2YWxpZGl0eSB0aGF0IHRoZSBvbGRlciBkcmFmdCBjb250YWlucyBzb21lIGluZm9ybWF0aW9u
IGJlaW5nIHVzZWQgaW4NCj4+PiB0aGUgbmV3IGRyYWZ0LCB5b3UgbWF5IHdhbnQgdG8gYWNrbm93
bGVkZ2UgdGhhdCBpbiB0aGUgcmVmZXJlbmNlcyBvcg0KPj4+IGFja25vd2xlZGdlbWVudHMuIEl0
IGFwcGVhcnMgdGhlIGRyYWZ0cyBhcmUgZGlzc2ltaWxhciBlbm91Z2ggdG8gbm90DQo+Pj4gYmUg
bWVyZ2VkIGJ1dCBJIG1heSBiZSB3cm9uZy4gUGxlYXNlIHNoYXJlIHlvdXIgb3BpbmlvbnMgb24g
dGhpcyBzbyB3ZQ0KPj4+IGNhbiBlc3RhYmxpc2ggY29uc2Vuc3VzIHdpdGhpbiB0aGUgZ3JvdXAg
YW5kIG1vdmUgdGhlIGRvY3VtZW50IGFsb25nLg0KPj4+DQo+Pj4gSWYgdGhlIGJyb2FkZXIgV0cg
cGFydGljaXBhbnRzIGhhdmUgYW4gb3BpbmlvbiBvbiB0aGlzIHBsZWFzZSBzcGVhayB1cC4NCj4+
Pg0KPj4+IHRoYW5rcywNCj4+PiBtaWtlDQo+Pj4NCj4+PiBPbiBUaHUsIE1heSA5LCAyMDEzIGF0
IDc6MzIgUE0sIFh1eGlhb2h1IDx4dXhpYW9odUBodWF3ZWkuY29tPiB3cm90ZToNCj4+PiA+IEhp
IGFsbCwNCj4+PiA+DQo+Pj4gPiBUaGlzIGRyYWZ0IHJlbWluZHMgbWUgdGhhdCB0aGVyZSBoYXMg
YmVlbiBhIGRyYWZ0DQo+Pj4gKGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXh1LXBp
bS1kcnByaW9yaXR5LWF1dG8tYWRqdXN0bWVudC0wMw0KPj4+ICkgdGhyZWUgeWVhcnMgYmVmb3Jl
IHdoaWNoIHVzZXMgYWxtb3N0IHRoZSBzYW1lIHRlY2hub2xvZ3kgdG8gc2F2ZQ0KPj4+IGFsbW9z
dCB0aGUgc2FtZSBwcm9ibGVtLg0KPj4+ID4NCj4+PiA+IFRoZSBmb2xsb3dpbmcgaXMgcXVvdGVk
IGZyb20gdGhlIGFib3ZlIGRyYWZ0Og0KPj4+ID4NCj4+PiA+ICAgICJJbiBmYWN0LCBpZiBWUlJQ
IGlzIHJ1biBvbiB0aGUgUElNIHJvdXRlcnMgYW5kIHRoZSBWUlJQIGhhcw0KPj4+ZW5hYmxlZA0K
Pj4+ID4gICAgdGhlIHVwc3RyZWFtIGxpbmsgdHJhY2tpbmcgbWVjaGFuaXNtLCB0aGUgUElNIERS
IGZhaWxvdmVyDQo+Pj5tZWNoYW5pc20NCj4+PiA+ICAgIGNvdWxkIGJlIGNvdXBsZWQgd2l0aCB0
aGUgVlJSUCBzbyBhcyB0byByZXVzZSB0aGUgdXBzdHJlYW0gbGluaw0KPj4+ID4gICAgdHJhY2tp
bmcgbWVjaGFuaXNtIG9mIFZSUlAuIE9uZSBvcHRpb24gaXMgdG8gc3luY2hyb25pemUgdGhlIFBJ
TQ0KPj4+RFINCj4+PiA+ICAgIHByaW9yaXR5IHZhbHVlIHRvIHRoZSBWUlJQIHByaW9yaXR5IHZh
bHVlIGFsd2F5cy4gSW4gdGhpcyB3YXksIHRoZQ0KPj4+ID4gICAgUElNIERSIGFuZCB0aGUgVlJS
UCBtYXN0ZXIgd2lsbCBhbHdheXMgcnVuIG9uIGFuIGlkZW50aWNhbCByb3V0ZXINCj4+PmlmDQo+
Pj4gPiAgICB0aGUgVlJSUCBQcmVlbXB0X01vZGUgaXMgc2V0IHRvIFRydWUuIEFub3RoZXIgb3B0
aW9uIGlzIHRvIG1ha2UNCj4+PnRoZQ0KPj4+ID4gICAgUElNIERSIGFuZCB0aGUgVlJSUCBtYXN0
ZXIgcnVuIG9uIGFuIGlkZW50aWNhbCByb3V0ZXIgYW55d2F5DQo+Pj4oaS5lLiwNCj4+PiA+ICAg
IHJlZ2FyZGxlc3Mgd2hldGhlciBvciBub3QgdGhlIFZSUlAgUHJlZW1wdF9Nb2RlIGlzIFRydWUp
LiBUbw0KPj4+YWNoaWV2ZQ0KPj4+ID4gICAgdGhpcyBnb2FsLCB0aGUgUElNIERSIHByaW9yaXR5
IG9mIHRoZSBWUlJQIG1hc3RlciByb3V0ZXIgU0hPVUxEDQo+Pj4gPiAgICBhbHdheXMgYmUgc2V0
IHRvIGEgaGlnaGVyIGZpeGVkIHZhbHVlIHRoYW4gdGhhdCBvZiB0aGUgVlJSUCBzbGF2ZQ0KPj4+
ID4gICAgcm91dGVyIGF1dG9tYXRpY2FsbHkuIg0KPj4+ID4NCj4+PiA+IEJlc3QgcmVnYXJkcywN
Cj4+PiA+IFhpYW9odQ0KPj4+ID4NCj4+PiA+PiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4+PiA+PiC3
orz+yMs6IHBpbS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86cGltLWJvdW5jZXNAaWV0Zi5vcmdd
ILT6se0NCj4+PiBNaWtlDQo+Pj4gPj4gTWNCcmlkZQ0KPj4+ID4+ILeiy83KsbzkOiAyMDEzxOo1
1MIxMMjVIDM6NDgNCj4+PiA+PiDK1bz+yMs6IHBpbUBpZXRmLm9yZw0KPj4+ID4+INb3zOI6IFtw
aW1dIGNhbGwgZm9yIGFkb3B0aW9uOiBkcmFmdC16aG91LXBpbS12cnJwLTAxDQo+Pj4gPj4NCj4+
PiA+PiBkcmFmdC16aG91LXBpbS12cnJwLTAxIHdhcyBwcmVzZW50ZWQgaW4gb3VyIG1vc3QgcmVj
ZW50IHBpbSBtZWV0aW5nDQo+Pj4gPj4gaW4gT3JsYW5kby4gNCBwZW9wbGUgd2VyZSBpbiBmYXZv
ciBvZiBhZG9wdGluZyB0aGUgZHJhZnQuIFplcm8NCj4+PmFnYWluc3QuDQo+Pj4gPj4gUGxlYXNl
IHJlYWQgdGhlIGRyYWZ0IChpdHMgc2hvcnQpIGFuZCBwcm92aWRlIGFuIG9waW5pb24gZWl0aGVy
IHdheQ0KPj4+ID4+IGJ5IHRoZSBlbmQgb2YgbmV4dCBGcmlkYXkgdGhlIDE3dGguDQo+Pj4gPj4N
Cj4+PiA+PiBodHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LXpob3UtcGltLXZycnAtMDEudHh0
DQo+Pj4gPj4NCj4+PiA+PiB0aGFua3MsDQo+Pj4gPj4gbWlrZQ0KPj4+ID4+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4gPj4gcGltIG1haWxpbmcg
bGlzdA0KPj4+ID4+IHBpbUBpZXRmLm9yZw0KPj4+ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vcGltDQoNCg==
