
From nobody Fri Aug  8 12:27:35 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E92BB1A00A8 for <pim@ietfa.amsl.com>; Fri,  8 Aug 2014 12:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zj2aGt9J-hrR for <pim@ietfa.amsl.com>; Fri,  8 Aug 2014 12:27:29 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2::152:127]) by ietfa.amsl.com (Postfix) with ESMTP id 648C71A0175 for <pim@ietf.org>; Fri,  8 Aug 2014 12:27:22 -0700 (PDT)
Received: from [IPv6:2001:420:301:1258:f57b:e47b:8027:5824] (unknown [IPv6:2001:420:301:1258:f57b:e47b:8027:5824]) by ufisa.uninett.no (Postfix) with ESMTPSA id A36D881CB for <pim@ietf.org>; Fri,  8 Aug 2014 21:27:20 +0200 (CEST)
Message-ID: <53E52496.8060508@venaas.com>
Date: Fri, 08 Aug 2014 12:27:18 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: pim@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/RM6xKuntP8shzCoa2DD8Pr58YlU
Subject: [pim] IETF 90 minutes
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Aug 2014 19:27:34 -0000

The minutes are finally posted at
http://www.ietf.org/proceedings/90/minutes/minutes-90-pim

Sorry for not doing this earlier. Let Mike and me know if you have any
corrections you want to make.

Stig


From nobody Sat Aug  9 12:28:44 2014
Return-Path: <sami.biz.email@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E94031A0393 for <pim@ietfa.amsl.com>; Sat,  9 Aug 2014 12:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.653
X-Spam-Level: 
X-Spam-Status: No, score=-0.653 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AYvvxlmMpBGL for <pim@ietfa.amsl.com>; Sat,  9 Aug 2014 12:28:41 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A23981A038F for <pim@ietf.org>; Sat,  9 Aug 2014 12:28:40 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id m15so6865794wgh.27 for <pim@ietf.org>; Sat, 09 Aug 2014 12:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=k1HcIKdbrTwvb4AbKlSQWwje5STqGOSqaO6B+jhstLU=; b=IwkqQc2p4J/kxppr5sybXyFbron8/urhJ94wN0KdtXDU8yKEJ2mfcBNenvwLhp7gLn QWMgQwbqtUza/u7DViVH7NqIhQLm7FyyC84k+YC2cqxz3USDCMnWkuidrJXmvZmTsKt2 Qvf+Es4vkk6WInIjvK5WzWvstuq4t5984nZlhV9GFTT0fCX4CdXeLof/tNeHVd3/95NP ai7/lUypTYR0nBYEgVhiSKhM8+QEKFKUQlCwngFb3c9SUHXr83cRT3guxOse7eb/iR34 Gp6ivTnmDJUOWi5vgSs3UJ7LNoRT7FISiU0rWHcRuYDwjDQOUZUNfsXZ6LRPhh1N9ye1 Kn1w==
X-Received: by 10.194.21.200 with SMTP id x8mr41086051wje.81.1407612519253; Sat, 09 Aug 2014 12:28:39 -0700 (PDT)
Received: from [192.168.1.6] ([178.253.58.71]) by mx.google.com with ESMTPSA id f6sm26597090wja.25.2014.08.09.12.28.37 for <multiple recipients> (version=TLSv1.2 cipher=AES128-GCM-SHA256 bits=128/128); Sat, 09 Aug 2014 12:28:38 -0700 (PDT)
Message-ID: <53E68466.3030209@gmail.com>
Date: Sat, 09 Aug 2014 23:58:22 +0330
From: saeed sami <sami.biz.email@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: pim@ietf.org
References: <mailman.105.1407611075.17744.pim@ietf.org>
In-Reply-To: <mailman.105.1407611075.17744.pim@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/ZmH1b9cQAXFmmSRGNAv77HFQwV0
Subject: Re: [pim] IETF 90 minutes
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Aug 2014 19:28:42 -0000

Hello.
just wanted to know if there has been any discussion/talk with regards 
to draft-sami-pim-ng.
thanks
On 08/09/2014 10:34 ب.ظ, pim-request@ietf.org wrote:
> Send pim mailing list submissions to
> 	pim@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/pim
> or, via email, send a message with subject or body 'help' to
> 	pim-request@ietf.org
>
> You can reach the person managing the list at
> 	pim-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pim digest..."
>
>
> Today's Topics:
>
>     1. IETF 90 minutes (Stig Venaas)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 08 Aug 2014 12:27:18 -0700
> From: Stig Venaas <stig@venaas.com>
> To: pim@ietf.org
> Subject: [pim] IETF 90 minutes
> Message-ID: <53E52496.8060508@venaas.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> The minutes are finally posted at
> http://www.ietf.org/proceedings/90/minutes/minutes-90-pim
>
> Sorry for not doing this earlier. Let Mike and me know if you have any
> corrections you want to make.
>
> Stig
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>
>
> ------------------------------
>
> End of pim Digest, Vol 124, Issue 1
> ***********************************


From nobody Tue Aug 12 11:34:12 2014
Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBE451A06C1 for <pim@ietfa.amsl.com>; Tue, 12 Aug 2014 11:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PSuecfL1nRmx for <pim@ietfa.amsl.com>; Tue, 12 Aug 2014 11:33:58 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2::152:127]) by ietfa.amsl.com (Postfix) with ESMTP id 76F241A06B3 for <pim@ietf.org>; Tue, 12 Aug 2014 11:33:58 -0700 (PDT)
Received: from [IPv6:2001:420:301:1258:39c8:883e:6768:d4db] (unknown [IPv6:2001:420:301:1258:39c8:883e:6768:d4db]) by ufisa.uninett.no (Postfix) with ESMTPSA id 97DEE81FA; Tue, 12 Aug 2014 20:33:56 +0200 (CEST)
Message-ID: <53EA5E0E.2010008@venaas.com>
Date: Tue, 12 Aug 2014 11:33:50 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: saeed sami <sami.biz.email@gmail.com>, pim@ietf.org
References: <mailman.105.1407611075.17744.pim@ietf.org> <53E68466.3030209@gmail.com>
In-Reply-To: <53E68466.3030209@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/_DbEZjEUekhU47-rwN4boH6yh58
Subject: Re: [pim] IETF 90 minutes
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Aug 2014 18:34:09 -0000

Hi

On 8/9/2014 1:28 PM, saeed sami wrote:
> Hello.
> just wanted to know if there has been any discussion/talk with regards
> to draft-sami-pim-ng.

I did ask people again to have a look at it and comment. I'm hoping some
people will provide feedback here on the list.

Stig

> thanks
> On 08/09/2014 10:34 ب.ظ, pim-request@ietf.org wrote:
>> Send pim mailing list submissions to
>>     pim@ietf.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>     https://www.ietf.org/mailman/listinfo/pim
>> or, via email, send a message with subject or body 'help' to
>>     pim-request@ietf.org
>>
>> You can reach the person managing the list at
>>     pim-owner@ietf.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of pim digest..."
>>
>>
>> Today's Topics:
>>
>>     1. IETF 90 minutes (Stig Venaas)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Fri, 08 Aug 2014 12:27:18 -0700
>> From: Stig Venaas <stig@venaas.com>
>> To: pim@ietf.org
>> Subject: [pim] IETF 90 minutes
>> Message-ID: <53E52496.8060508@venaas.com>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> The minutes are finally posted at
>> http://www.ietf.org/proceedings/90/minutes/minutes-90-pim
>>
>> Sorry for not doing this earlier. Let Mike and me know if you have any
>> corrections you want to make.
>>
>> Stig
>>
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> pim mailing list
>> pim@ietf.org
>> https://www.ietf.org/mailman/listinfo/pim
>>
>>
>> ------------------------------
>>
>> End of pim Digest, Vol 124, Issue 1
>> ***********************************
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


From nobody Fri Aug 15 02:18:16 2014
Return-Path: <ice@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B093A1A0981 for <pim@ietfa.amsl.com>; Fri, 15 Aug 2014 02:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.169
X-Spam-Level: 
X-Spam-Status: No, score=-15.169 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ee4MURXc2CD for <pim@ietfa.amsl.com>; Fri, 15 Aug 2014 02:18:09 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1E2B1A0961 for <pim@ietf.org>; Fri, 15 Aug 2014 02:18:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32467; q=dns/txt; s=iport; t=1408094290; x=1409303890; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=sUtQK4Y58SZLLah1aPlPhFwmLGfOtquf2XAxSxvCv+U=; b=JlyqWAQilaUT23YF4Ljj9cK1o2sd4V4OxSAtM7gqNtL/SVgnIqS06VX3 d+ELOvhV02zcgBTjg6GWaV6SjtBh3I8ifJOs6l0RxoPSOaSyi2QtxRQIA X66NPhJlLlLdF9UszFRqCOtvB5wOz80sINhiBc7CafpXCyfHGJchcbCcp E=;
X-Files: draft-ietf-pim-explicit-rpf-vector-05.txt : 15818
X-IronPort-AV: E=Sophos;i="5.01,869,1400025600";  d="txt'?scan'208";a="142609743"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 15 Aug 2014 09:18:08 +0000
Received: from [10.61.196.45] ([10.61.196.45]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s7F9I1Wh002990 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 15 Aug 2014 09:18:06 GMT
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/mixed; boundary="Apple-Mail=_A686DE8A-6EA0-4AFD-8F7C-B8DCAEDA3D07"
From: IJsbrand Wijnands <ice@cisco.com>
X-Priority: 1
In-Reply-To: <CAG4d1rfxVLdnkSQHGStye_m+-Nr=PxUak97TKwr79nSs8hsaZg@mail.gmail.com>
Date: Fri, 15 Aug 2014 11:18:00 +0200
Message-Id: <D57E272D-6EA2-4393-9C40-C30E23336AB3@cisco.com>
References: <008e01cf1a88$eefd3600$ccf7a200$@olddog.co.uk> <533BC9AE.8020602@cisco.com> <061601cf4e9b$adb85570$09290050$@olddog.co.uk> <85DAD28B-6A14-4BEB-B324-816A0FFA347D@cisco.com> <CAG4d1rebTqG3Y7b8iDMTRSZJoCzyhomuCi4poAcohsPsc_Za3w@mail.gmail.com> <537A8F27.40205@cisco.com> <CAG4d1rfxVLdnkSQHGStye_m+-Nr=PxUak97TKwr79nSs8hsaZg@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/lvI_vuzOQ4lLqe1U5SiOTwZrFrI
Cc: draft-ietf-pim-explicit-rpf-vector.all@tools.ietf.org, Alia Atlas <akatlas@juniper.net>, pim@ietf.org, Javed Asghar <jasghar@cisco.com>
Subject: Re: [pim] AD review of draft-ietf-pim-explicit-rpf-vector
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Aug 2014 09:18:13 -0000

--Apple-Mail=_A686DE8A-6EA0-4AFD-8F7C-B8DCAEDA3D07
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Alia,

Really sorry for the delay in responding to your comments. I=92ve taken =
over the editor role from Javed and will drive it forward.

> Comments from review:
>=20
> Sec 10:  If the RPF vector isn't understood, isn't the path taken by
> the traffic not going to conform to that desire?  I agree that the
> possibility for loops is bad if the explicit RPF vector remained - but
> I am also concerned that there's no way to tell that the desired path
> wasn't taken - in terms of errors reported or so on.   I don't see a

Yes, you=92re right, but this is also the nature of the beast ;-) PIM =
does not have any back signalling to indicate failures or notifications =
regarding the status of the tree being build.

> protocol based way of forcing an error to be returned or capability
> checking - so I'm expecting to see a small paragraph that talks about
> the requirement in terms of manageability for computing the explicit
> path and perhaps using mtrace to verify.   If you have a better
> suggestion, I would love to see it.

How the explicit path is determined is outside the scope of the draft.=20=


Whether or not the PIM tree is broken due to unicast routing, wrong RPF =
vector (RFC5496), or wrong explicit RPF vector on the stack (this =
draft), the same existing tools can be used to troubleshoot it, like =
mtrace. I don=92t think this draft introduces different requirements.=20

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

Good question. The RPF vector stack carried within the PIM join is =
routing information that avoids a RIB lookup at each node. Suppose there =
is a change in the vector stack that makes the RPF interface change from =
A to B. This is treated as a RPF change that could have occurred due to =
a RIB update, no difference there. If you want to make the RPF change =
using Make-Before-Break you could, but its not a requirement introduced =
by this draft.

I think you=92re overall concern is mostly about how do you guarantee =
the vector stack is consistent and managed, and users of this draft =
should be aware of the consequences of incorrect vectors. I=92ve added =
the following text, does that address your concerns?

=97=97
   This document describes the procedures to carry Explicit RPF vectors
   in PIM, but it does not introduce any new mechanism in PIM to
   validate the correctness of the RPF vectors.  It is up to the
   mechanism(s) that produce the Explicit RPF Vectors to ensure they are
   correct.  Existing mechanisms like [I-D.ietf-mboned-mtrace-v2] may be
   used to verify how the PIM tree was build.
=97


>=20
> Nits:
> Figure 1 - the figure is not properly aligned

Fixed.

I=92ve attached the updated draft,

Thx,

Ice.=

--Apple-Mail=_A686DE8A-6EA0-4AFD-8F7C-B8DCAEDA3D07
Content-Disposition: attachment;
	filename=draft-ietf-pim-explicit-rpf-vector-05.txt
Content-Type: text/plain;
	name="draft-ietf-pim-explicit-rpf-vector-05.txt"
Content-Transfer-Encoding: quoted-printable





Network Working Group                                          J. Asghar
Internet-Draft                                         IJ. Wijnands, Ed.
Intended status: Standards Track                         S. Krishnaswamy
Expires: February 16, 2015                                      A. Karan
                                                           Cisco Systems
                                                                 V. Arya
                                                            DIRECTV Inc.
                                                         August 15, 2014


                          Explicit RPF Vector
               draft-ietf-pim-explicit-rpf-vector-05.txt

Abstract

   The PIM Reverse Path Forwarding (RPF) Vector TLV defined in RFC 5496
   can be included in a PIM Join Attribute such that the RPF neighbor is
   selected based on the unicast reachability of the RPF Vector instead
   of the Source or RP associated with the multicast tree.

   This document defines a new RPF Vector Attribute type such that an
   explicit RPF neighbor list can be encoded in the PIM Join Attribute,
   bypassing the unicast route lookup.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 16, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents



Asghar, et al.          Expires February 16, 2015               [Page 1]
=0C
Internet-Draft             Explicit RPF Vector               August 2014


   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Use of the PIM Explicit RPF Vector  . . . . . . . . . . . . .   4
   5.  Explicit RPF Vector Attribute . . . . . . . . . . . . . . . .   4
   6.  Mixed Vector Processing . . . . . . . . . . . . . . . . . . .   4
   7.  Conflicting RPF Vectors . . . . . . . . . . . . . . . . . . .   5
   8.  PIM Asserts . . . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Join Suppression  . . . . . . . . . . . . . . . . . . . . . .   5
   10. Unsupported Explicit Vector Handling  . . . . . . . . . . . .   5
   11. Explicit RPF Vector Attribute TLV Format  . . . . . . . . . .   5
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   13. Security Considerations . . . . . . . . . . . . . . . . . . .   6
   14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   15. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     15.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     15.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The procedures in [RFC5496] define how a RPF vector can be used to
   influence the path selection in the absence of a route to the source.
   The same procedures can be used to override a route to the source
   when it exists.  It is possible to include multiple RPF vectors in
   the list where each router along the path will perform a unicast
   route lookup on the first vector in the attribute list.  Once the
   router owning the address of the RPF vector is reached, following the
   procedures in [RFC5496], the RPF vector will be removed from the
   attribute list.  This will result in a 'loosely' routed path based on
   the unicast reachability of the RPF vector(s).  We call this
   'loosely' because we still depend on unicast routing reachability to
   the RPF Vector.

   In some scenarios we don't want to rely on the unicast reachability
   to the RPF vector address and we want to build a path strictly based
   on the RPF vectors.  In that case the RPF vectors represent a list of
   directly connected PIM neighbors along the path.  For these vectors



Asghar, et al.          Expires February 16, 2015               [Page 2]
=0C
Internet-Draft             Explicit RPF Vector               August 2014


   we MUST NOT do a unicast route lookup.  We call these 'Explicit' RPF
   Vector addresses.  If a router receiving an Explicit RPF Vector does
   not have a PIM neighbor matching the Explicit RPF Vector address it
   MUST NOT fall back to loosely routing the join.  Instead, it may
   process the packet and store the RPF Vector list so that the PIM join
   may be sent out as soon as the neighbor comes up.  Since the behavior
   of the Explicit RPF Vector differs from the loose RPF vector as
   defined [RFC5496], we're defining a new attribute called the Explicit
   RPF Vector.

   This document defines a new TLV in the PIM Join Attribute message
   [RFC5384] for specifying the explicit path.

2.  Specification of Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Motivation

   Some broadcast video transport networks use a multicast PIM Live-Live
   resiliency model for video delivery based on PIM SSM or PIM ASM.
   Live-Live implies using 2 active spatially diverse multicast trees to
   transport video flows from root to leaf multicast routers.  The leaf
   multicast router receives 2 copies from the PIM multicast core and
   will replicate 1 copy towards the receivers [I-D.ietf-rtgwg-mofrr].

   One of the requirements of the PIM Live-Live resiliency model is to
   ensure path-diversity of the 2 active PIM trees in the core such that
   they do not intersect to avoid a single point of failure.  IGP routed
   RPF paths of 2 PIM trees could be routed over the same transit router
   and create a single point of failure.  It is useful to have a way to
   specify the explicit path along which the PIM join is propagated.

   How the Explicit RPF Vector list is determined is outside the scope
   of this document.  For example, it may either be manually configured
   by the network operator or procedures may be implemented on the
   egress router to dynamically calculate the vector list based on a
   link state database protocol, like OSPF or IS-IS.

   Due to the fact that the leaf router receives two copies of the
   multicast stream via two diverse paths, there is no need for PIM to
   repair the broken path immediately.  It is up to the egress router to
   either wait for the broken path to be repaired or build a new
   explicit path using a new RPF vector list.  Which method is applied
   depends very much on how the vector list was determined initially.




Asghar, et al.          Expires February 16, 2015               [Page 3]
=0C
Internet-Draft             Explicit RPF Vector               August 2014


   Double failures are not considered and are outside the scope of this
   document.

   This document describes the procedures to carry Explicit RPF vectors
   in PIM, but it does not introduce any new mechanism in PIM to
   validate the correctness of the RPF vectors.  It is up to the
   mechanism(s) that produce the Explicit RPF Vectors to ensure they are
   correct.  Existing mechanisms like [I-D.ietf-mboned-mtrace-v2] may be
   used to verify how the PIM tree was build.

4.  Use of the PIM Explicit RPF Vector

   Figure 1 provides an example multicast join path
   R4->R3->R6->R5->R2->R1, where the multicast join is explicitly routed
   to the source hop-by-hop using the Explicit RPF Vector list.  When
   R5-R6 link fails the join will NOT take an alternate path.


   [S]---(R1)--(R2)---(R3)--(R4)---[R]
          <---   |      |  ---
             |   |      |  |
             | (R5)---(R6) |
             - (S,G) Join -


                                 Figure 1

   In comparison, when [RFC5496] procedures are used, if R5-R6 link
   fails then the join may be re-routed using R6-R8-R7 path to reach R5.

5.  Explicit RPF Vector Attribute

   This draft uses PIM join attribute type TBD1 by IANA for specifying
   an Explicit RPF Vector.

6.  Mixed Vector Processing

   Explicit RPF Vector attribute does not impact or restrict the
   functionality of other RPF vector attributes in a PIM join.  It is
   possible to mix vectors of different types, such that some part of
   the tree is explicit and other parts are loosely routed.  RPF vectors
   are processed in the order in which they are specified.  That is, the
   first RPF vector attribute is looked at and processed, it can be
   either loose or explicit.







Asghar, et al.          Expires February 16, 2015               [Page 4]
=0C
Internet-Draft             Explicit RPF Vector               August 2014


7.  Conflicting RPF Vectors

   It is possible that a PIM router has multiple downstream neighbors.
   If for the same multicast route there is an inconsistency between the
   Explicit RPF Vector lists provided by the downstream PIM neighbor,
   the procedures as documented in section 3.3.3 [RFC5384] apply.

8.  PIM Asserts

   Section 3.3.3 of [RFC5496] specifies the procedures for how to deal
   with PIM asserts when RPF vectors are used.  The same procedures
   apply to the Explicit RPF Vector.  There is minor behavioral
   difference, the route metric that is included in the PIM Assert
   should be the route metric of the first Explicit RPF vector address
   in the list.  However, the first Explicit vector should always be
   directly connected, so the Metric may likely be zero.  The Metric
   will therefore not be a tie breaker in the PIM Assert selection
   procedure.

9.  Join Suppression

   Section 3.3.4 of [RFC5496] specifies the procedures how to apply join
   suppression when an RPF Vector attribute is included in the PIM join.
   The same procedure applies to the Explicit RPF Vector attribute.  The
   procedure MUST match against all the Explicit RPF Vectors in the PIM
   join before a PIM join can be suppressed.

10.  Unsupported Explicit Vector Handling

   The F bit MUST be set to 0 in all Explicit RPF vectors in case the
   upstream router receiving the join does not support the TLV.  As
   described in section 3.3.2 of [RFC5384], routers that do not
   understand the type of a particular attribute that has the F bit
   clear will discard it and continue to process the join.

   This processing is particularly important when the routers that do
   not support the Explicit RPF TLV are identified as hops in the
   explicit RPF list, because failing to remove the RPF vectors could
   cause upstream routers to send the join back toward these routers
   causing loops.

11.  Explicit RPF Vector Attribute TLV Format









Asghar, et al.          Expires February 16, 2015               [Page 5]
=0C
Internet-Draft             Explicit RPF Vector               August 2014


    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |F|E| Type      | Length        |        Value
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-.......

                                 Figure 2

   F bit:  The F bit MUST be set to 0.  Otherwise there could be loops.

   E bit:  End of Attributes.  If this bit is set then this is the last
      TLV specified in the list.

   Type:  The Vector Attribute type is TBD1.

   Length:  Length depending on the Address Family of the Encoded-
      Unicast address.

   Value:  Encoded-Unicast address.  This could be a valid primary or
      secondary address.

12.  IANA Considerations

   A new attribute (TBD1) type from the "PIM Join Attribute Types"
   registry needs to be assigned by IANA for the Explicit RPF Vector
   attribute.  The proposed value 4.

13.  Security Considerations

   Security of the Explicit RPF Vector Attribute is only guaranteed by
   the security of the PIM packet, so the security considerations for
   PIM Join packets as described in PIM-SM [RFC4601] apply here.
   Additionally, the Explicit RPF Vector list should be subject to a
   policy to validate the list consists of a valid path before its used
   by a receiver to build a multicast tree.

14.  Acknowledgments

   The authors would like to thank Vatsa Kumar, Nagendra Kumar and
   Bharat Joshi for the comments on the document.

15.  References

15.1.  Normative References







Asghar, et al.          Expires February 16, 2015               [Page 6]
=0C
Internet-Draft             Explicit RPF Vector               August 2014


   [I-D.ietf-rtgwg-mofrr]
              Karan, A., Filsfils, C., Farinacci, D., Wijnands, I.,
              Decraene, B., Joorde, U., and W. Henderickx, "Multicast
              only Fast Re-Route", draft-ietf-rtgwg-mofrr-04 (work in
              progress), May 2014.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC4601]  Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
              "Protocol Independent Multicast - Sparse Mode (PIM-SM):
              Protocol Specification (Revised)", RFC 4601, August 2006.

   [RFC5384]  Boers, A., Wijnands, I., and E. Rosen, "The Protocol
              Independent Multicast (PIM) Join Attribute Format", RFC
              5384, November 2008.

   [RFC5496]  Wijnands, IJ., Boers, A., and E. Rosen, "The Reverse Path
              Forwarding (RPF) Vector TLV", RFC 5496, March 2009.

15.2.  Informative References

   [I-D.ietf-mboned-mtrace-v2]
              Asaeda, H. and W. Lee, "Mtrace Version 2: Traceroute
              Facility for IP Multicast", draft-ietf-mboned-mtrace-v2-10
              (work in progress), July 2013.

Authors' Addresses

   Javed Asghar
   Cisco Systems
   725, Alder Drive
   Milpitas  CA 95035
   USA

   Email: jasghar@cisco.com


   IJsbrand Wijnands (editor)
   Cisco Systems
   De Kleetlaan 6a
   Diegem  1831
   Belgium

   Email: ice@cisco.com






Asghar, et al.          Expires February 16, 2015               [Page 7]
=0C
Internet-Draft             Explicit RPF Vector               August 2014


   Sowmya Krishnaswamy
   Cisco Systems
   3750 Cisco Way
   San Jose  CA 95134
   USA

   Email: sowkrish@cisco.com


   Apoorva Karan
   Cisco Systems
   3750 Cisco Way
   San Jose  CA 95134
   USA

   Email: apoorva@cisco.com


   Vishal Arya
   DIRECTV Inc.
   2230 E Imperial Hwy
   El Segundo  CA  90245
   USA

   Email: varya@directv.com


























Asghar, et al.          Expires February 16, 2015               [Page 8]

--Apple-Mail=_A686DE8A-6EA0-4AFD-8F7C-B8DCAEDA3D07
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


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


--Apple-Mail=_A686DE8A-6EA0-4AFD-8F7C-B8DCAEDA3D07--


From nobody Mon Aug 25 14:22:16 2014
Return-Path: <mike.mcbride@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9EB1A0383 for <pim@ietfa.amsl.com>; Mon, 25 Aug 2014 14:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level: 
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KaX8D8B9eT6r for <pim@ietfa.amsl.com>; Mon, 25 Aug 2014 14:22:07 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AC651A037A for <pim@ietf.org>; Mon, 25 Aug 2014 14:22:07 -0700 (PDT)
X-AuditID: c6180641-f79916d00000623a-c4-53fb51df17b7
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id F0.EE.25146.FD15BF35; Mon, 25 Aug 2014 17:10:23 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0174.001; Mon, 25 Aug 2014 17:21:58 -0400
From: Mike McBride <mike.mcbride@ericsson.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: PIM + VRRP final call for adoption
Thread-Index: Ac/AqmEcBwVMshAlSJicj11wq8oDXA==
Date: Mon, 25 Aug 2014 21:21:57 +0000
Message-ID: <6F5149063CE40341BE7953160A93C5A0F67D1D@eusaamb109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/alternative; boundary="_000_6F5149063CE40341BE7953160A93C5A0F67D1Deusaamb109ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyuXRPgu79wN/BBlcv6Fp8eXiT2YHRY8mS n0wBjFFcNimpOZllqUX6dglcGT9uv2EtWGta0bTLvIHxr24XIyeHhICJxPKW6+wQtpjEhXvr 2boYuTiEBI4ySqzd8o4VwlnOKDFpURczSBWbgJ7E6YXNrCC2iICiRPvcFjBbWEBbYm3jZ6i4 gcTdHTOZIWw9iQMzbrGA2CwCqhI/3k8Ci/MKeEtsP9XLBGIzAm3+fmoNmM0sIC5x68l8JoiL BCSW7DnPDGGLSrx8/I8VwlaSmPP6GjNEfb7EkdmHWSFmCkqcnPmEZQKj0Cwko2YhKZuFpAwi riOxYPcnNghbW2LZwtfMMPaZA4+ZkMUXMLKvYuQoLU4ty003MtzECAz8YxJsjjsYF3yyPMQo wMGoxMOrwPk7WIg1say4MvcQozQHi5I4r2b1vGAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFIN jPPUbqYtavn2X8eIs39GRsLtDes+y+pXnsv9k8MXV+S+rU3z/dHPNyd/Ob42abbbxklyxduf W4X82yZ6wEV09RN2Hbktm9Y8PnWC31VWub3/ck/V5g9SNRW/thvlnDRrmD7vgu/n5WU+KkEb ThnnbeH/qlvt3+9+Pynt1ctVwfd8g1gfaKxa3K7EUpyRaKjFXFScCADsnap4XQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/tmLT7OsydQQcQihT0C4dRZdcLTs
Subject: [pim] PIM + VRRP final call for adoption
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Aug 2014 21:22:14 -0000

--_000_6F5149063CE40341BE7953160A93C5A0F67D1Deusaamb109ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Howdy,

As a follow up to our meeting in Toronto, we need to again discuss this spe=
cific draft (http://www.ietf.org/id/draft-zhou-pim-vrrp-02.txt) on the list=
, one last time. As you look at the minutes below, you'll see that we had a=
nother discussion about whether to adopt the draft and the relevancy of the=
 work in general. There are good opinions for and against adoption of this =
draft. We haven't reached consensus to adopt. This is a last call to hear y=
our opinions either way. Please speak up. If we can reach consensus we will=
 adopt. If we cannot reach consensus we will recommend the author to submit=
 an individual, non wg, submission.

Thank you for sharing your opinions, we are a friendly group, don't be shy.

mike

...
PIM WG IETF90 Toronto: July 22nd: 1640-1840

draft-zhou-pim-vrrp: Mike (not on agenda, impromptu slides ;)

Lenny : Don't use VRRP. Use unicast routing protocols to solve the problem.

Herman: Customers have seen this issue. Some solution needed.

Stig: Solution in the document has been implemented and shipping.

Mike: WG adoption poll (again!) on mailing list.

Stig: Individual submission - question to Alia on thoughts.

Alia: Can go as independent submission, if it doesn't hurt anything
architecturally. Will not be an AD sponsored work. If it's a real problem,
why not solve in WG. Discuss on list (maybe there is a better solution).

Lenny: It is a real problem, since things break. Rather than run PIM, run
unicast routing protocol. Unicast protocol should be much simpler to run
than a multicast protocol.

Stig: Customer are using static routing protocol. Hence the need.
...

--_000_6F5149063CE40341BE7953160A93C5A0F67D1Deusaamb109ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Howdy,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As a follow up to our meeting in Toronto, we need to=
 again discuss this specific draft (<a href=3D"http://www.ietf.org/id/draft=
-zhou-pim-vrrp-02.txt">http://www.ietf.org/id/draft-zhou-pim-vrrp-02.txt</a=
>) on the list, one last time. As you
 look at the minutes below, you&#8217;ll see that we had another discussion=
 about whether to adopt the draft and the relevancy of the work in general.=
 There are good opinions for and against adoption of this draft. We haven&#=
8217;t reached consensus to adopt. This is a
 last call to hear your opinions either way. Please speak up. If we can rea=
ch consensus we will adopt. If we cannot reach consensus we will recommend =
the author to submit an individual, non wg, submission.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thank you for sharing your opinions, we are a friend=
ly group, don&#8217;t be shy.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">mike<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8230;<o:p></o:p></p>
<p class=3D"MsoNormal">PIM WG IETF90 Toronto: July 22nd: 1640-1840<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">draft-zhou-pim-vrrp: Mike (not on agenda, impromptu =
slides ;)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Lenny : Don&#8217;t use VRRP. Use unicast routing pr=
otocols to solve the problem.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Herman: Customers have seen this issue. Some solutio=
n needed.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Stig: Solution in the document has been implemented =
and shipping.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Mike: WG adoption poll (again!) on mailing list. <o:=
p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Stig: Individual submission - question to Alia on th=
oughts. <o:p>
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Alia: Can go as independent submission, if it doesn&=
#8217;t hurt anything<o:p></o:p></p>
<p class=3D"MsoNormal">architecturally. Will not be an AD sponsored work. I=
f it&#8217;s a real problem,<o:p></o:p></p>
<p class=3D"MsoNormal">why not solve in WG. Discuss on list (maybe there is=
 a better solution).
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Lenny: It is a real problem, since things break. Rat=
her than run PIM, run<o:p></o:p></p>
<p class=3D"MsoNormal">unicast routing protocol. Unicast protocol should be=
 much simpler to run<o:p></o:p></p>
<p class=3D"MsoNormal">than a multicast protocol. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Stig: Customer are using static routing protocol. He=
nce the need.<o:p></o:p></p>
<p class=3D"MsoNormal">&#8230;<o:p></o:p></p>
</div>
</body>
</html>

--_000_6F5149063CE40341BE7953160A93C5A0F67D1Deusaamb109ericsso_--


From nobody Tue Aug 26 14:08:50 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D3C1A0217 for <pim@ietfa.amsl.com>; Tue, 26 Aug 2014 14:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fU0oh07CsvUX for <pim@ietfa.amsl.com>; Tue, 26 Aug 2014 14:08:43 -0700 (PDT)
Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 046861A02D8 for <pim@ietf.org>; Tue, 26 Aug 2014 14:08:42 -0700 (PDT)
Received: by mail-yh0-f48.google.com with SMTP id i57so12466968yha.21 for <pim@ietf.org>; Tue, 26 Aug 2014 14:08:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wdgyHhsjaYPOqwq57gytE+r+paf3iJhWlGqnBiMR8e4=; b=Idpm8qjhueA+mf/5MoMgu5MkSmND7/1pJwAIpGRNqnT26ynWWuityG04E1n6cibYY0 jzwrlRl9ednjGlMKEqhyWRwEE1qzUZh7w317tFzy+LB5ifF+1o8vhq2sza0katAVZwWq eT6pZtQm53ixbcAp/jKFS6xs8g05qmm9TNR/vy+PYaLnArkhaZYTHUFj0T32j3mul6EM jRfnjEmMykSSNd7LqIxNebZJQ81Pq6IKR4Tn4aIhUKPS2lzBPArXtPsDOOPqpNZqWRrk flWK3y0ArWyAXJJjbE385T5fbX6FOHY1cKAKiKQSaWi66zaf602kBkogfgVbU5d3S6hk J+5A==
MIME-Version: 1.0
X-Received: by 10.236.133.165 with SMTP id q25mr45825180yhi.62.1409087322280;  Tue, 26 Aug 2014 14:08:42 -0700 (PDT)
Received: by 10.170.110.17 with HTTP; Tue, 26 Aug 2014 14:08:42 -0700 (PDT)
In-Reply-To: <D57E272D-6EA2-4393-9C40-C30E23336AB3@cisco.com>
References: <008e01cf1a88$eefd3600$ccf7a200$@olddog.co.uk> <533BC9AE.8020602@cisco.com> <061601cf4e9b$adb85570$09290050$@olddog.co.uk> <85DAD28B-6A14-4BEB-B324-816A0FFA347D@cisco.com> <CAG4d1rebTqG3Y7b8iDMTRSZJoCzyhomuCi4poAcohsPsc_Za3w@mail.gmail.com> <537A8F27.40205@cisco.com> <CAG4d1rfxVLdnkSQHGStye_m+-Nr=PxUak97TKwr79nSs8hsaZg@mail.gmail.com> <D57E272D-6EA2-4393-9C40-C30E23336AB3@cisco.com>
Date: Tue, 26 Aug 2014 17:08:42 -0400
Message-ID: <CAG4d1rchO8ZnuUz4Sxx1=hqYSk_oPndT8vnAmbv11zzZn4CYAQ@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: IJsbrand Wijnands <ice@cisco.com>
Content-Type: multipart/alternative; boundary=20cf303a32c94d5c5005018eb563
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/Q53ewc2CHeJdGsRlog1ykO-Ah1A
Cc: draft-ietf-pim-explicit-rpf-vector.all@tools.ietf.org, Alia Atlas <akatlas@juniper.net>, pim@ietf.org, Javed Asghar <jasghar@cisco.com>
Subject: Re: [pim] AD review of draft-ietf-pim-explicit-rpf-vector
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Aug 2014 21:08:47 -0000

--20cf303a32c94d5c5005018eb563
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ice,


On Fri, Aug 15, 2014 at 5:18 AM, IJsbrand Wijnands <ice@cisco.com> wrote:

> Hi Alia,
>
> Really sorry for the delay in responding to your comments. I=E2=80=99ve t=
aken over
> the editor role from Javed and will drive it forward.
>

Ok.   Could you please also respond to Jeffrey's comments in
http://www.ietf.org/mail-archive/web/pim/current/msg02993.html ?  I asked
him for a review as well, due to my concerns.

> Comments from review:
> >
> > Sec 10:  If the RPF vector isn't understood, isn't the path taken by
> > the traffic not going to conform to that desire?  I agree that the
> > possibility for loops is bad if the explicit RPF vector remained - but
> > I am also concerned that there's no way to tell that the desired path
> > wasn't taken - in terms of errors reported or so on.   I don't see a
>
> Yes, you=E2=80=99re right, but this is also the nature of the beast ;-) P=
IM does
> not have any back signalling to indicate failures or notifications
> regarding the status of the tree being build.


Right - so you get a best-effort attempt to follow the RPF vector.  At a
minimum,
there should be something about manageability or operational concerns here.


> > protocol based way of forcing an error to be returned or capability
> > checking - so I'm expecting to see a small paragraph that talks about
> > the requirement in terms of manageability for computing the explicit
> > path and perhaps using mtrace to verify.   If you have a better
> > suggestion, I would love to see it.
>
> How the explicit path is determined is outside the scope of the draft.
>
> Whether or not the PIM tree is broken due to unicast routing, wrong RPF
> vector (RFC5496), or wrong explicit RPF vector on the stack (this draft),
> the same existing tools can be used to troubleshoot it, like mtrace. I
> don=E2=80=99t think this draft introduces different requirements.


Then say so - b/c you have silent failures and no details on how the paths
could or should be
computed.



> > I do feel that this mechanism is under-specified in the context of how
> > it is to be used.  For example, is make-before-break important?  What
> > about knowing that the new path is fully created before modifying the
> > other one for live-live?  How is any of this coordinated if there are
> > multiple leaf-nodes independently determining the explicit RPF vector
> > to use?  I do see Sec 7 discussing how to handle conflicts - but I
> > don't see any consideration of the dynamics of that solution or why it
> > is a good choice (beyond being a choice and in RFC 5384).
>
> Good question. The RPF vector stack carried within the PIM join is routin=
g
> information that avoids a RIB lookup at each node. Suppose there is a
> change in the vector stack that makes the RPF interface change from A to =
B.
> This is treated as a RPF change that could have occurred due to a RIB
> update, no difference there. If you want to make the RPF change using
> Make-Before-Break you could, but its not a requirement introduced by this
> draft.
>
> I think you=E2=80=99re overall concern is mostly about how do you guarant=
ee the
> vector stack is consistent and managed, and users of this draft should be
> aware of the consequences of incorrect vectors. I=E2=80=99ve added the fo=
llowing
> text, does that address your concerns?
>
> =E2=80=94=E2=80=94
>    This document describes the procedures to carry Explicit RPF vectors
>    in PIM, but it does not introduce any new mechanism in PIM to
>    validate the correctness of the RPF vectors.  It is up to the
>    mechanism(s) that produce the Explicit RPF Vectors to ensure they are
>    correct.  Existing mechanisms like [I-D.ietf-mboned-mtrace-v2] may be
>    used to verify how the PIM tree was build.
> =E2=80=94
>

It helps.  I'm also concerned that conflicts for the explicit rpf vector
differences aren't clearly articulated.

Finally - I really don't see this as being informational.  Either it's
experimental or, since the chairs believe that it has WG consensus, it is
standards track.

Thanks,
Alia


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

--20cf303a32c94d5c5005018eb563
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Ice,<br><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Aug 15, 2014 at 5:1=
8 AM, IJsbrand Wijnands <span dir=3D"ltr">&lt;<a href=3D"mailto:ice@cisco.c=
om" target=3D"_blank">ice@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Hi Alia,<br>
<br>
Really sorry for the delay in responding to your comments. I=E2=80=99ve tak=
en over the editor role from Javed and will drive it forward.<br></blockquo=
te><div><br></div><div>Ok. =C2=A0 Could you please also respond to Jeffrey&=
#39;s comments in <a href=3D"http://www.ietf.org/mail-archive/web/pim/curre=
nt/msg02993.html">http://www.ietf.org/mail-archive/web/pim/current/msg02993=
.html</a> ? =C2=A0I asked him for a review as well, due to my concerns.=C2=
=A0</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<div class=3D"">&gt; Comments from review:<br>
&gt;<br>
&gt; Sec 10:=C2=A0 If the RPF vector isn&#39;t understood, isn&#39;t the pa=
th taken by<br>
&gt; the traffic not going to conform to that desire?=C2=A0 I agree that th=
e<br>
&gt; possibility for loops is bad if the explicit RPF vector remained - but=
<br>
&gt; I am also concerned that there&#39;s no way to tell that the desired p=
ath<br>
&gt; wasn&#39;t taken - in terms of errors reported or so on.=C2=A0 =C2=A0I=
 don&#39;t see a<br>
<br>
</div>Yes, you=E2=80=99re right, but this is also the nature of the beast ;=
-) PIM does not have any back signalling to indicate failures or notificati=
ons regarding the status of the tree being build.</blockquote><div><br></di=
v><div>
Right - so you get a best-effort attempt to follow the RPF vector. =C2=A0At=
 a minimum,</div><div>there should be something about manageability or oper=
ational concerns here.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le=
ft-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=3D"">
&gt; protocol based way of forcing an error to be returned or capability<br=
>
&gt; checking - so I&#39;m expecting to see a small paragraph that talks ab=
out<br>
&gt; the requirement in terms of manageability for computing the explicit<b=
r>
&gt; path and perhaps using mtrace to verify.=C2=A0 =C2=A0If you have a bet=
ter<br>
&gt; suggestion, I would love to see it.<br>
<br>
</div>How the explicit path is determined is outside the scope of the draft=
.<br>
<br>
Whether or not the PIM tree is broken due to unicast routing, wrong RPF vec=
tor (RFC5496), or wrong explicit RPF vector on the stack (this draft), the =
same existing tools can be used to troubleshoot it, like mtrace. I don=E2=
=80=99t think this draft introduces different requirements.</blockquote>
<div><br></div><div>Then say so - b/c you have silent failures and no detai=
ls on how the paths could or should be</div><div>computed. =C2=A0</div><div=
><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,20=
4);border-left-style:solid;padding-left:1ex">
<div class=3D"">
&gt; I do feel that this mechanism is under-specified in the context of how=
<br>
&gt; it is to be used.=C2=A0 For example, is make-before-break important?=
=C2=A0 What<br>
&gt; about knowing that the new path is fully created before modifying the<=
br>
&gt; other one for live-live?=C2=A0 How is any of this coordinated if there=
 are<br>
&gt; multiple leaf-nodes independently determining the explicit RPF vector<=
br>
&gt; to use?=C2=A0 I do see Sec 7 discussing how to handle conflicts - but =
I<br>
&gt; don&#39;t see any consideration of the dynamics of that solution or wh=
y it<br>
&gt; is a good choice (beyond being a choice and in RFC 5384).<br>
<br>
</div>Good question. The RPF vector stack carried within the PIM join is ro=
uting information that avoids a RIB lookup at each node. Suppose there is a=
 change in the vector stack that makes the RPF interface change from A to B=
. This is treated as a RPF change that could have occurred due to a RIB upd=
ate, no difference there. If you want to make the RPF change using Make-Bef=
ore-Break you could, but its not a requirement introduced by this draft.<br=
>

<br>
I think you=E2=80=99re overall concern is mostly about how do you guarantee=
 the vector stack is consistent and managed, and users of this draft should=
 be aware of the consequences of incorrect vectors. I=E2=80=99ve added the =
following text, does that address your concerns?<br>

<br>
=E2=80=94=E2=80=94<br>
=C2=A0 =C2=A0This document describes the procedures to carry Explicit RPF v=
ectors<br>
=C2=A0 =C2=A0in PIM, but it does not introduce any new mechanism in PIM to<=
br>
=C2=A0 =C2=A0validate the correctness of the RPF vectors.=C2=A0 It is up to=
 the<br>
=C2=A0 =C2=A0mechanism(s) that produce the Explicit RPF Vectors to ensure t=
hey are<br>
=C2=A0 =C2=A0correct.=C2=A0 Existing mechanisms like [I-D.ietf-mboned-mtrac=
e-v2] may be<br>
=C2=A0 =C2=A0used to verify how the PIM tree was build.<br>
<div class=3D"">=E2=80=94<br></div></blockquote><div><br></div><div>It help=
s. =C2=A0I&#39;m also concerned that conflicts for the explicit rpf vector =
differences aren&#39;t clearly articulated.</div><div><br></div><div>Finall=
y - I really don&#39;t see this as being informational. =C2=A0Either it&#39=
;s experimental or, since the chairs believe that it has WG consensus, it i=
s standards track.</div>
<div>=C2=A0</div><div>Thanks,</div><div>Alia=C2=A0</div><div><br></div><div=
><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex">
<div class=3D"">&gt;<br>
&gt; Nits:<br>
&gt; Figure 1 - the figure is not properly aligned<br>
<br>
</div>Fixed.<br>
<br>
I=E2=80=99ve attached the updated draft,<br>
<br>
Thx,<br>
<br>
Ice.<br><br>
&gt;<br>
&gt; Regards,<br>
&gt; Alia<br>
&gt;<br>
&gt;<br>
&gt; On Mon, May 19, 2014 at 7:09 PM, Javed Asghar &lt;<a href=3D"mailto:ja=
sghar@cisco.com">jasghar@cisco.com</a>&gt; wrote:<br>
&gt;&gt; Hi Alia,<br>
&gt;&gt;<br>
&gt;&gt; Did you get a chance to review? Its been awhile.<br>
&gt;&gt; If its ok, we&#39;d like to move it forward.<br>
&gt;&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt; -Javed.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On 4/3/2014 3:11 PM, Alia Atlas wrote:<br>
&gt;&gt;<br>
&gt;&gt; Thanks for updating the draft.=C2=A0 I will review it very soon so=
 we can get it<br>
&gt;&gt; moving along.<br>
&gt;&gt;<br>
&gt;&gt; Alia<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Thu, Apr 3, 2014 at 9:07 AM, IJsbrand Wijnands &lt;<a href=3D"m=
ailto:ice@cisco.com">ice@cisco.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks Adrian,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Forwarded to Alia who now has the joy of being your AD.<br=
>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; From me, just to note that you cannot demand a code point =
from IANA, you<br>
&gt;&gt;&gt;&gt; can only request one. The way to do it is to use the TBD f=
orm of the text I<br>
&gt;&gt;&gt;&gt; suggested and then say. &quot;It is requested that IANA as=
sign the value 4.&quot;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; We&#39;ll change it to say &#39;requested&#39;.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Note for future reference that if you feel an attachment f=
or a specific<br>
&gt;&gt;&gt;&gt; code point you really, really need to apply for an early a=
llocation (RFC<br>
&gt;&gt;&gt;&gt; 7120) because someone else might come along in the interve=
ning time and use<br>
&gt;&gt;&gt;&gt; your value for something else.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Yes, we know about that. I remember discussing it with Stig at=
 one point,<br>
&gt;&gt;&gt; but since this was the only draft in the queue to request such=
 value I think<br>
&gt;&gt;&gt; the conclusion was that its not necessary to do early allocati=
on, but your<br>
&gt;&gt;&gt; right, we should really always do that to be safe.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thx,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Ice.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Adrian<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; From: Javed Asghar [mailto:<a href=3D"mailto:jasghar@cisco=
.com">jasghar@cisco.com</a>]<br>
&gt;&gt;&gt;&gt; Sent: 02 April 2014 09:26<br>
&gt;&gt;&gt;&gt; To: <a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.c=
o.uk</a>; draft-ietf-pim-explicit-rpf-vector<br>
&gt;&gt;&gt;&gt; Subject: Re: AD review of draft-ietf-pim-explicit-rpf-vect=
or<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Submitted updated draft:<br>
&gt;&gt;&gt;&gt; <a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-=
pim-explicit-rpf-vector-04.txt" target=3D"_blank">http://www.ietf.org/inter=
net-drafts/draft-ietf-pim-explicit-rpf-vector-04.txt</a><br>
&gt;&gt;&gt;&gt; Please see comments inline below.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;&gt; -Javed.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 1/26/2014 3:22 AM, Adrian Farrel wrote:<br>
&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I have done my usual AD review of this document after rece=
iving the<br>
&gt;&gt;&gt;&gt; publication request. The purpose of the review is to catch=
 and fix<br>
&gt;&gt;&gt;&gt; any issues that might otherwise show up in IETF last call =
or IESG<br>
&gt;&gt;&gt;&gt; review. This helps smooth the passage of the document late=
r and also<br>
&gt;&gt;&gt;&gt; increases the quality text.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; This seems like a good and simple proposal, and I don&#39;=
t want to bog<br>
&gt;&gt;&gt;&gt; it down. But there are a number of small editorial issues =
and a<br>
&gt;&gt;&gt;&gt; couple of technical questions included below.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I have put the document into &quot;Revised I-D Needed&quot=
; state and will<br>
&gt;&gt;&gt;&gt; wait to see an updated version before I start the IETF las=
t call.<br>
&gt;&gt;&gt;&gt; But please feel free to debate any of these points with me=
.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Thanks for the work.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Adrian<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; You need to fix the idnits before I can put this to IETF l=
ast call.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - Missing page breaks<br>
&gt;&gt;&gt;&gt; - 2119 boilerplate broken (you have &quot;SHALL&quot; &quo=
t;NOT&quot;)<br>
&gt;&gt;&gt;&gt; - there is a line too long<br>
&gt;&gt;&gt;&gt; - missing reference for [draft-mofrr-karan]<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; [Shepherd - Your write-up says no nits found. How come?]<b=
r>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Conventionally we have used the term &quot;strict&quot; in=
 counterpoint to<br>
&gt;&gt;&gt;&gt; &quot;loose&quot; to describe hops, and termed the whole p=
ath &quot;explicit&quot;. I<br>
&gt;&gt;&gt;&gt; don&#39;t suppose this matters: you are defining your own =
terms for a<br>
&gt;&gt;&gt;&gt; new application in PIM.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; However, this has led to some confusion in the text becaus=
e of the<br>
&gt;&gt;&gt;&gt; normal use of the English word &quot;explicit&quot;. For e=
xample, the Abstract<br>
&gt;&gt;&gt;&gt; says:<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0This document defines a new Reverse Path Forwa=
rding (RPF) Vector<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0TLV to build multicast trees via an explicit p=
ath sent in the PIM<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0join.<br>
&gt;&gt;&gt;&gt; ...which doesn&#39;t give any clue to the distinction betw=
een this work<br>
&gt;&gt;&gt;&gt; and RFC 5496. You might be better with something like:<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0The PIM Reverse Path Forwarding (RPF) Vector T=
LV defined in RFC 5496<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0can be included in a PIM Join Attribute to all=
ow a leaf to apply<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0controls to the path of a multicast tree. This=
 document defines a<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0new Vector Attribute type so that an RPF Vecto=
r TLV can be used to<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0indicate that the unicast address indicated in=
 the TLV must be used<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0as the next hop in the multicast tree.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; This kind of language could usefully be repeated throughou=
t the<br>
&gt;&gt;&gt;&gt; document.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Updated<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 1<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0For some applications, it might be useful to h=
ave a way to specify<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0the explicit path along which the PIM join is =
propagated.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Could you possibly be a little less vague? :-)<br>
&gt;&gt;&gt;&gt; If this is the level of certainty you have for the utility=
 of your work<br>
&gt;&gt;&gt;&gt; then it shouldn&#39;t be on the Standards Track. Fortunate=
ly, you *do* have<br>
&gt;&gt;&gt;&gt; a good use case later in the document.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I suggest re-ordering paragraphs:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 3, 4, 2<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ...and delete paragraph 1.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Updated.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Suggest to rename Section 3 &quot;Motivation&quot;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Updated<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 3<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; As noted above, you need to provide the reference for<br>
&gt;&gt;&gt;&gt; [draft-mofrr-karan]. But actually, I wonder whether you re=
ally need to<br>
&gt;&gt;&gt;&gt; include the citation as the text in the paragraph seems to=
 hold up well<br>
&gt;&gt;&gt;&gt; without any further explanation.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Updated.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 3<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0It might be useful to have a way to specify th=
e explicit path<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0along which the PIM join is propagated.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I think you established that it *is* useful in the previou=
s text.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Corrected.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 3<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0How the Explicit RPF Vector list is determined=
 is outside the<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0scope of this document. It may either be manua=
lly configured by<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0the network operator or procedures may be impl=
emented on the<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0egress router to dynamically calculate the vec=
tor list based on<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0a link state database protocol, like OSPF or I=
S-IS.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I agree that this should be out of scope and you should sa=
y so.<br>
&gt;&gt;&gt;&gt; However, having said it is out of scope, why do you go on =
to<br>
&gt;&gt;&gt;&gt; discuss it?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Ack. This is implementation specific. We ha=
ve changed this<br>
&gt;&gt;&gt;&gt; discussion as example. This was feedback from previous rev=
iews.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; You should give more clarity as to why an RPF list using 5=
496 list<br>
&gt;&gt;&gt;&gt; entries would not be good enough. In Figure 1 it would app=
ear that the<br>
&gt;&gt;&gt;&gt; list {R4, R3, R6, R5, R2, R1} would work just fine using 5=
496.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Added more clarity with a comparison betwee=
n Explicit RPF Vector<br>
&gt;&gt;&gt;&gt; and RFC5496 procedures.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 5<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0This draft uses PIM join attribute type 4 for =
specifying an Explicit<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0RPF Vector.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Please make this:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0This draft uses PIM join attribute type TBD by=
 IANA for specifying an<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0Explicit RPF Vector.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Updated.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 7 is describing, for example, simple network with =
source S and<br>
&gt;&gt;&gt;&gt; leafs R1 and R2...<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 A=C2=A0 =C2=A0R1<br>
&gt;&gt;&gt;&gt; / \ /<br>
&gt;&gt;&gt;&gt; S=C2=A0 =C2=A0C<br>
&gt;&gt;&gt;&gt; \ / \<br>
&gt;&gt;&gt;&gt;=C2=A0 B=C2=A0 =C2=A0R2<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ...where R1 sends explicit RPF TLVs {C, A} and that path i=
s set up.<br>
&gt;&gt;&gt;&gt; Then R2 sends explicit RPF TLVs {C, B}.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 3.3.3 of RFC 5384 is cited as the tie-breaker.<br>
&gt;&gt;&gt;&gt; This is OK, but it appears to say that the Explicit RPF is=
 not<br>
&gt;&gt;&gt;&gt; mandatory. It would be nice to make it very clear that a r=
eceiver has<br>
&gt;&gt;&gt;&gt; no expectations that the explicit RPF list it supplies wil=
l actually be<br>
&gt;&gt;&gt;&gt; used.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; There is no change in our draft with respec=
t to this behavior and<br>
&gt;&gt;&gt;&gt; its documented well in RFC 5384 section 3.3.3. Adding more=
 text could<br>
&gt;&gt;&gt;&gt; confuse the reader. We felt the current text is sufficient=
. Let us know if<br>
&gt;&gt;&gt;&gt; this is ok with you.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 10<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; This is important material to include, but I think it need=
s some work.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0The F bit MUST be set to 0 by a downstream rou=
ter in the join that<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0is sent to the upstream router that does not s=
upport Explicit RPF<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0vector.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; But the downstream router doesn&#39;t know whether the ups=
tream router<br>
&gt;&gt;&gt;&gt; supports the new vector or not! So I think you need...<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0The F bit MUST be set to 0 in all Explicit RPF=
 vectors in case the<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0upstream router receiving the join does not su=
pport the TLV. As<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0described in section 3.3.2 of [RFC5384], route=
rs that do not<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0understand the type of a particular attribute =
that has the F bit<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0clear will discard it and continue to process =
the join.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0This processing is particularly important when=
 the routers that<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0do not support the Explicit RPF TLV are identi=
fied as hops in the<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0explicit RPF list, because failing to remove t=
he RPF vectors could<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0cause upstream routers to send the join back t=
oward these routers<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0causing loops.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Updated. Thanks for the clarity. Its very p=
recise.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; However, this doesn&#39;t seem to be the only way that loo=
ps can be caused<br>
&gt;&gt;&gt;&gt; (referring back to section 9).<br>
&gt;&gt;&gt;&gt; I don&#39;t see this mentioned in RFC 5496 either, but sur=
ely:<br>
&gt;&gt;&gt;&gt; - the RPF list could contain an explicit loop<br>
&gt;&gt;&gt;&gt; - the use of loose hops with poorly ordered list entries c=
ould create a<br>
&gt;&gt;&gt;&gt;=C2=A0 loop<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; It is fine to note that this is caught by normal PIM proce=
ssing, but<br>
&gt;&gt;&gt;&gt; you should say so, and you should say what happens to the =
join. It<br>
&gt;&gt;&gt;&gt; seems to me that 3.3.4 of 5496 only catches the case where=
 join is<br>
&gt;&gt;&gt;&gt; targeting the same upstream neighbor. But the sequential l=
ist nature<br>
&gt;&gt;&gt;&gt; of the RPF list means that the loop might not be &quot;end=
less&quot; but could<br>
&gt;&gt;&gt;&gt; still be a loop. How is this caught and handled?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Please note that the explicit or loose RPF =
vector list at every<br>
&gt;&gt;&gt;&gt; hop will consume the RPF vector entry. If an explicit or l=
oose RPF vector<br>
&gt;&gt;&gt;&gt; list is constructed poorly (eg. mis-config) the processing=
 of the RPF vector<br>
&gt;&gt;&gt;&gt; is still as described in RFC 5496 and doesn&#39;t need to =
change. We need to fix<br>
&gt;&gt;&gt;&gt; the user error.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 11<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Please replace...<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; OLD<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0Type<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0----<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0The Vector Attribute type is 4.<br>
&gt;&gt;&gt;&gt; NEW<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0Type<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0----<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0The Vector Attribute type is TBD by IANA.<br>
&gt;&gt;&gt;&gt; END<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ---<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; We would like to request type 4 attribute f=
rom IANA explicitly.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Section 13 seems light!<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The RPF list (and especially the explicit RPF) provides a =
way to<br>
&gt;&gt;&gt;&gt; cause traffic to take different routes through the network=
. This<br>
&gt;&gt;&gt;&gt; could be used to cause traffic to take expensive paths, to=
 be<br>
&gt;&gt;&gt;&gt; routed through hot parts of the network, or to be directed=
 to<br>
&gt;&gt;&gt;&gt; snooping nodes.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; This means that the existence of the RPF TLV makes the use=
 of<br>
&gt;&gt;&gt;&gt; security in PIM more important to prevent tampering with t=
he RPF<br>
&gt;&gt;&gt;&gt; list.<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Good point.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; But it also raises a question of policy and authorization.=
 Clearly,<br>
&gt;&gt;&gt;&gt; when a receiver seeks to join a multicast tree, it must be=
<br>
&gt;&gt;&gt;&gt; authenticated for that join. But additionally, you may wan=
t to note<br>
&gt;&gt;&gt;&gt; that the inclusion of an RPF list by a receiver should be =
subject to<br>
&gt;&gt;&gt;&gt; policy.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; JA&gt;&gt;&gt; Updated.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; .<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; pim mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:pim@ietf.org">pim@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pim" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/pim</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
<br>
<br></blockquote></div><br></div></div>

--20cf303a32c94d5c5005018eb563--


From nobody Thu Aug 28 01:56:53 2014
Return-Path: <ice@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9155E1A6EEF for <pim@ietfa.amsl.com>; Thu, 28 Aug 2014 01:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.169
X-Spam-Level: 
X-Spam-Status: No, score=-15.169 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55e7WzE2dvJb for <pim@ietfa.amsl.com>; Thu, 28 Aug 2014 01:56:38 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8749B1A6EEC for <pim@ietf.org>; Thu, 28 Aug 2014 01:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14316; q=dns/txt; s=iport; t=1409216197; x=1410425797; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=N5Mbivhx3/FI/0NUw0nmQ64jvbzhnebpRsdCaM7ffv0=; b=JaV+HMpUrX6SOT1kYFKqcgw1x2TjxKfW+a804IYHVUJNJ4thTM7LAD/b 0Zu1yx046Q00SgoWyXis4x8yv7lZtvZvSEu2Qm7MYV7tSsLfQHfrlws+Y UiLDrhQzSXVF8cuH0jFWOZ6I39EvpiOPlioK4r90PqY9+xYc9EVk9UEW7 Q=;
X-IronPort-AV: E=Sophos;i="5.04,416,1406592000"; d="scan'208";a="151855162"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 28 Aug 2014 08:56:35 +0000
Received: from ams-iwijnand-8812.cisco.com (ams-iwijnand-8812.cisco.com [10.60.202.83]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s7S8uYsq000501 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 28 Aug 2014 08:56:35 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <CAG4d1rchO8ZnuUz4Sxx1=hqYSk_oPndT8vnAmbv11zzZn4CYAQ@mail.gmail.com>
Date: Thu, 28 Aug 2014 10:56:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8025080F-C4C0-4282-A4D8-20384B032119@cisco.com>
References: <008e01cf1a88$eefd3600$ccf7a200$@olddog.co.uk> <533BC9AE.8020602@cisco.com> <061601cf4e9b$adb85570$09290050$@olddog.co.uk> <85DAD28B-6A14-4BEB-B324-816A0FFA347D@cisco.com> <CAG4d1rebTqG3Y7b8iDMTRSZJoCzyhomuCi4poAcohsPsc_Za3w@mail.gmail.com> <537A8F27.40205@cisco.com> <CAG4d1rfxVLdnkSQHGStye_m+-Nr=PxUak97TKwr79nSs8hsaZg@mail.gmail.com> <D57E272D-6EA2-4393-9C40-C30E23336AB3@cisco.com> <CAG4d1rchO8ZnuUz4Sxx1=hqYSk_oPndT8vnAmbv11zzZn4CYAQ@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/sSqjIfzZNB6WIHzMpxwJ2PGOYYk
Cc: draft-ietf-pim-explicit-rpf-vector.all@tools.ietf.org, Alia Atlas <akatlas@juniper.net>, pim@ietf.org, Javed Asghar <jasghar@cisco.com>
Subject: Re: [pim] AD review of draft-ietf-pim-explicit-rpf-vector
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2014 08:56:45 -0000

Hi Alia,

Thanks for the comments.

> Ok.   Could you please also respond to Jeffrey's comments in =
http://www.ietf.org/mail-archive/web/pim/current/msg02993.html ?  I =
asked him for a review as well, due to my concerns.=20

Yes, will do.

> I think you=92re overall concern is mostly about how do you guarantee =
the vector stack is consistent and managed, and users of this draft =
should be aware of the consequences of incorrect vectors. I=92ve added =
the following text, does that address your concerns?
>=20
> =97=97
>    This document describes the procedures to carry Explicit RPF =
vectors
>    in PIM, but it does not introduce any new mechanism in PIM to
>    validate the correctness of the RPF vectors.  It is up to the
>    mechanism(s) that produce the Explicit RPF Vectors to ensure they =
are
>    correct.  Existing mechanisms like [I-D.ietf-mboned-mtrace-v2] may =
be
>    used to verify how the PIM tree was build.
> =97
>=20
> It helps.  I'm also concerned that conflicts for the explicit rpf =
vector differences aren't clearly articulated.

Ok, that relates to Jeffrey=92s comments, right?

>=20
> Finally - I really don't see this as being informational.  Either it's =
experimental or, since the chairs believe that it has WG consensus, it =
is standards track.

I had already changed it to =91Standards Track=92 in version-05 that I =
attached :-)

Thx,

Ice.

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


From nobody Fri Aug 29 01:33:48 2014
Return-Path: <ice@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 937061A035C for <pim@ietfa.amsl.com>; Fri, 29 Aug 2014 01:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.169
X-Spam-Level: 
X-Spam-Status: No, score=-15.169 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s90AbaCRkHki for <pim@ietfa.amsl.com>; Fri, 29 Aug 2014 01:33:46 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 131861A0306 for <pim@ietf.org>; Fri, 29 Aug 2014 01:33:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2003; q=dns/txt; s=iport; t=1409301226; x=1410510826; h=from:content-transfer-encoding:subject:date:message-id: cc:to:mime-version; bh=G+4ZXWToE/YxiuFkcOKLHsE7gHBR9/+YwOZoszvdF8o=; b=JwzE9VPKgV/FqtQIFrTyB6d6lsPy4nTipA62ERQJYIqGGasfZqSyXkCS G+fFJ/FWG1zf5XNRQYMPtK1Ow2eeE9LB9Bb47YF6Q44UbWXWDRLHO2ayG wPedz1gELIzoqbMlNcxqUiDG0LFKCfZ1NKp6uh+oiDPUwAGM4LH7RlaI5 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikKABE6AFStJssW/2dsb2JhbABbs0EFAQVpnz2BJ3eEBQR6BRaBI4hNCLtGF4V8iVCDNoEdBZgZhEOVHYNgO4J+AQEB
X-IronPort-AV: E=Sophos;i="5.04,423,1406592000"; d="scan'208";a="157872936"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 29 Aug 2014 08:33:42 +0000
Received: from ams-iwijnand-8812.cisco.com (ams-iwijnand-8812.cisco.com [10.60.202.83]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s7T8Xg2A019182 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Aug 2014 08:33:42 GMT
From: IJsbrand Wijnands <ice@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Aug 2014 10:33:38 +0200
Message-Id: <AF6B84D7-3150-4F0A-8497-0EB46FE21B29@cisco.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/15bENVImV3wStlo0D_9yba4wp0I
Cc: pim@ietf.org
Subject: Re: [pim] I-D Action: draft-ietf-pim-explicit-rpf-vector-04.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Aug 2014 08:33:47 -0000

Hi Jeffrey,

Thanks so much for the comments, see below.

> I noticed that the spec does not talk about what to do when it =
receives some loose rpf vectors from one downstream neighbor and
> some strict ones from another neighbor - section 6 talks about mixed =
ones in the same join, and section 7 refers to section 3.3.3
> [RFC5384], which is about conflicts between the same type.

I agree, this needs to be fixed.

How about the following additional text to section 7.:

---
The conflict resolution procedures in section 3.3.3 [RFC5384] only apply =
to attributes of the same Join Attribute type. Join Attributes that have =
a different type can=92t be compared because the content of the Join =
Attribute may have a totally different meaning and/or encoding. This may =
cause a problem if a mix of Explicit RPF Vectors (this document) and =
=91loose=92 RPF vectors [RFC5496] is received from two or more =
downstream routers. The order in which the RPF vectors are encoded may =
be different and/or the combination of RPF vectors may be inconsistent. =
The procedures in section 3.3.3 [RFC5384] would not resolve the =
conflict. The following procedures MUST be applied to deal with this =
scenario.

A router processing =91Explicit=92 or =91Loose=92 RPF Vectors MUST =
verify that the order in which RPF Vectors types appear in the PIM Join =
Attribute list received from its downstream PIM neighbors are equal. =
Once it is determined the RPF Vector types are on the stack are equal, =
the content of the RPF Vectors MUST be compared ([RFC5384]). If it is =
determined that there is either a conflict with RPF Vector types or the =
RPF Vector content, we use the RPF Vector stack from the PIM adjacency =
with the numerically smallest IP address. In the case of IPv6, the link =
local address will be used. When two neighbors have the same IP address, =
either for IPv4 or IPv6, the interface index MUST be used as a tie =
breaker.=20
---

Thx,

Ice.=


From nobody Sun Aug 31 22:39:50 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 465C61A0024; Sun, 31 Aug 2014 22:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1gE4nZgTRH4M; Sun, 31 Aug 2014 22:39:43 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9627B1A0022; Sun, 31 Aug 2014 22:39:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p5
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140901053941.10423.26368.idtracker@ietfa.amsl.com>
Date: Sun, 31 Aug 2014 22:39:41 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/pim/fjRZ1L260SAlXITFX0_eoUHpJRU
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-explicit-tracking-10.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 05:39:45 -0000

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

        Title           : IGMP/MLD-Based Explicit Membership Tracking Function for Multicast Routers
        Author          : Hitoshi Asaeda
	Filename        : draft-ietf-pim-explicit-tracking-10.txt
	Pages           : 10
	Date            : 2014-08-31

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


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

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

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


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

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

