
From nobody Thu Jun  2 09:18:47 2016
Return-Path: <farinacci@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3312512B05A; Thu,  2 Jun 2016 09:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUZMJKJAUkzB; Thu,  2 Jun 2016 09:18:41 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F47312D18B; Thu,  2 Jun 2016 09:18:41 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id c127so54704044ywb.1; Thu, 02 Jun 2016 09:18:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0zV5ZZxHmSshZz1U/NfAMmIJ63qm76Uq5O1pLGCqRUs=; b=RsYdf1DAOSb5tYn4h2Hb+RdykJNQ4du2zBZRJ7ZaqMF5WUFNCmFBBnFcxV7cuvVaEF gdFWC+YsfaQgNH4jrY6C52gtNJ/+X5rR0YKsO/1tGstrYLortrGXq+43koSFMl9kNFWj Cvbqvi//gZBcPZxwwnO6q5gBeysItb4r9kettJqzeQDpW6fCBJYaVG9pce5elHDat43R 3csYjJDNkKWOZRaMOVlAQYCs2sPpDIZ7l1S9N1l7kgGOV78mv8SPUMD/E/f6D+hzo+HT 0u4Ocim2j4ouyt9WZTPRKvnPzWGQmYR9Y6UfpXej4jRV/gJB38lPbFsHkxEls7uY2mn2 +rVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0zV5ZZxHmSshZz1U/NfAMmIJ63qm76Uq5O1pLGCqRUs=; b=Xc+qlgg7027HYLp5eL3AbDdDRUHUoOQEeTUwCFwLomNnj0hnB0Z26PfRiIejV25Iot aMxxj0PEsbJa5DZtKGkGibUV7QjdWx/ndEnRpq0qKq179TbbkLQGd91hCVHEnkLjvRCp 3rb7DHKYo4xmwpQxVVc+tt8DtAx73P+hVj0M+bzCGScp8E9kDCl9EIY9iSmdtprPVel5 Ry08SwqOn7eDMjbLSagP07HATyjQuCCCQsLZHl34eX4aARoT4eOpy2pZ78EZAeib6yi6 HpkEMfgYq7O83ioZEsWXksjaIyER5ACyu0ogS0S7kLW3udumE1Z6VhVHnphUuzw17Pyy Qk6g==
X-Gm-Message-State: ALyK8tIKtkYW+gDJxU9ndoinbgjhju8JpZ+nXaDZIR49/AFHeSzdH/RvTFCBV+zrDIsYxg==
X-Received: by 10.13.221.142 with SMTP id g136mr6256089ywe.238.1464884320639;  Thu, 02 Jun 2016 09:18:40 -0700 (PDT)
Received: from [192.168.0.153] (50-81-93-18.client.mchsi.com. [50.81.93.18]) by smtp.gmail.com with ESMTPSA id w192sm645311ywd.34.2016.06.02.09.18.39 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Jun 2016 09:18:40 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CAHANBtLwOyLj1h95u6zdxfX5i-7Qm_QiC9AQyvfYthzcN3ErVQ@mail.gmail.com>
Date: Thu, 2 Jun 2016 09:18:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <85D2EE99-2064-45B5-9F11-F4DCD4B2D5C6@gmail.com>
References: <8CCB28152EA2E14A96BBEDC15823481A09E4D861@dfweml501-mbx> <CAHANBtLwOyLj1h95u6zdxfX5i-7Qm_QiC9AQyvfYthzcN3ErVQ@mail.gmail.com>
To: Stig Venaas <stig@venaas.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/Yuoci9_CZ0UbYVHLyutEl8wY2fk>
Cc: LISP mailing list list <lisp@ietf.org>, pim@ietf.org
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 16:18:43 -0000

> We're doing a last call on this document in the pim wg right now. As
> this is used to support LISP multicast (RFC 6831) we would appreciate
> review and feedback from the lisp wg as well. This document has been
> presented and discussed in the lisp wg before.

I have some comments. See inline.

>    To support mobility of EIDs, the root xTR must keep track of ALL
>    receiver RLOCs even when the corresponding downstream site has not
>    requested unicast replication.  The root xTR may detect that a =
local
>    multicast source "root-EID" has moved to a remote LISP site.  Under
>    such circumstances LISP sends a SMR message to all receiver xTRs,
>    prompting them to update their map cache.  This is only possible if
>    LISP can obtain from PIM the set of all receiver RLOCS that have
>    active Join state for the root-EID.

This paragraph does not make it clear if the EID that is moving is the =
root-EID or the receiver host that moves to another LISP site where =
there may be a new receiver-RLOC for head-end replication.

The reason I say that is because the way the paragraph starts, but as it =
continues, it is referring to the root-EID changing. And when you say =
=E2=80=9CLISP sends a SMR message=E2=80=9D it doesn=E2=80=99t say if the =
old root-xTR sends it or the new root-xTR the root-EID move into does.

So are you trying to inform the receiver-xTRs to tell the new root-xTR =
about some new state? Like for instance, start joining the (root-RLOC, =
G) in the underlay? If so, this paragraph I thought was for head-end =
replication.

So in any event, I=E2=80=99m completely confused on (1) what event is =
occurring, and (2) what the mechanism is and (3) why you are doing the =
action you are doing.

Dino=


From nobody Thu Jun  2 16:58:42 2016
Return-Path: <jearango@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 090DA12D616; Thu,  2 Jun 2016 16:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level: 
X-Spam-Status: No, score=-15.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEyWqln0jJeN; Thu,  2 Jun 2016 16:58:38 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A17612D603; Thu,  2 Jun 2016 16:58:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10012; q=dns/txt; s=iport; t=1464911918; x=1466121518; h=from:to:subject:date:message-id:mime-version; bh=pEL63MDO5kQJQTz8L9sC7D0p4gtVWJG/kRd+qJkytHg=; b=mkePo3aybTSj/VyGy/oR7HNwkwAxbe5+KLET46gnE9GFCiF0HWbjpUbh LgzwXGsvA0DD9onwPagYiI1FQTKfVFZoeik20WAE1QZrpYv/0HEilPjdX YH6B0M5R1f/GORgvLBn6rBtqmgFFMpzGgutStJ5YIWkCwKlZx1CS4MPJm o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A1AgBlx1BX/5ldJa1egm1NVoEDtUuCa?= =?us-ascii?q?oIPgXmHRzgUAQEBAQEBAWUnhEYBBAEtUQ0BCHgmAQQBGogfCMJdAQEBAQEFAQE?= =?us-ascii?q?BAQEBAQEfhieETYoaBZg4AYZvhymBcI0zhjOJGAEeNoIHHIFLimt/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,409,1459814400";  d="scan'208,217";a="279571763"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jun 2016 23:58:37 +0000
Received: from XCH-ALN-010.cisco.com (xch-aln-010.cisco.com [173.36.7.20]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u52NwbKm003330 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 2 Jun 2016 23:58:37 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-010.cisco.com (173.36.7.20) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 2 Jun 2016 18:58:36 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1104.009; Thu, 2 Jun 2016 18:58:36 -0500
From: "Jesus Arango (jearango)" <jearango@cisco.com>
To: Dino Farinacci <farinacci@gmail.com>, "pim@ietf.org" <pim@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "Stig Venaas (svenaas)" <stig@cisco.com>
Thread-Topic: Re: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03
Thread-Index: AdG9Jym58u0x1P1uR625NPI8omge+w==
Date: Thu, 2 Jun 2016 23:58:36 +0000
Message-ID: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.25.132]
Content-Type: multipart/alternative; boundary="_000_ead4d10adfe946f3afaae63b784d301eXCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/blgskVhiBkpB0l1amvu0yJlMeTA>
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 23:58:41 -0000

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

Hi Dino,

The paragraph refers to the root EID moving. Do you think the following cor=
rections are sufficient?

To support mobile multicast sources, the root xTR must keep track of ALL re=
ceiver RLOCs even when the corresponding receiver XTRs have not requested u=
nicast replication.  If the root xTR detects that the root-EID has moved to=
 a new root xTR, it sends an SMR message to all receiver xTRs,  prompting t=
hem to update their map cache.  This is only possible if  LISP can obtain f=
rom PIM the set of all receiver RLOCS that have active Join state for the r=
oot-EID.

Thanks
Jesus



> We're doing a last call on this document in the pim wg right now. As
> this is used to support LISP multicast (RFC 6831) we would appreciate
> review and feedback from the lisp wg as well. This document has been
> presented and discussed in the lisp wg before.

I have some comments. See inline.

>    To support mobility of EIDs, the root xTR must keep track of ALL
>    receiver RLOCs even when the corresponding downstream site has not
>    requested unicast replication.  The root xTR may detect that a local
>    multicast source "root-EID" has moved to a remote LISP site.  Under
>    such circumstances LISP sends a SMR message to all receiver xTRs,
>    prompting them to update their map cache.  This is only possible if
>    LISP can obtain from PIM the set of all receiver RLOCS that have
>    active Join state for the root-EID.

This paragraph does not make it clear if the EID that is moving is the root=
-EID or the receiver host that moves to another LISP site where there may b=
e a new receiver-RLOC for head-end replication.

The reason I say that is because the way the paragraph starts, but as it co=
ntinues, it is referring to the root-EID changing. And when you say "LISP s=
ends a SMR message" it doesn't say if the old root-xTR sends it or the new =
root-xTR the root-EID move into does.

So are you trying to inform the receiver-xTRs to tell the new root-xTR abou=
t some new state? Like for instance, start joining the (root-RLOC, G) in th=
e underlay? If so, this paragraph I thought was for head-end replication.

So in any event, I'm completely confused on (1) what event is occurring, an=
d (2) what the mechanism is and (3) why you are doing the action you are do=
ing.

Dino

--_000_ead4d10adfe946f3afaae63b784d301eXCHALN008ciscocom_
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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	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"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Hi Dino,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">The paragraph refer=
s to the root EID moving. Do you think the following corrections are suffic=
ient?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">To support mobile m=
ulticast sources, the root xTR must keep track of ALL receiver RLOCs even w=
hen the corresponding receiver XTRs have not requested unicast replication.=
&nbsp; If the root xTR detects that the root-EID
 has moved to a new root xTR, it sends an SMR message to all receiver xTRs,=
&nbsp; prompting them to update their map cache.&nbsp; This is only possibl=
e if&nbsp; LISP can obtain from PIM the set of all receiver RLOCS that have=
 active Join state for the root-EID.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Thanks<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Jesus<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt; We're doing a =
last call on this document in the pim wg right now. As<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt; this is used t=
o support LISP multicast (RFC 6831) we would appreciate<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt; review and fee=
dback from the lisp wg as well. This document has been<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt; presented and =
discussed in the lisp wg before.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">I have some comment=
s. See inline.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt;&nbsp;&nbsp;&nb=
sp; To support mobility of EIDs, the root xTR must keep track of ALL<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt;&nbsp;&nbsp;&nb=
sp; receiver RLOCs even when the corresponding downstream site has not<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt;&nbsp;&nbsp;&nb=
sp; requested unicast replication.&nbsp; The root xTR may detect that a loc=
al<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt;&nbsp;&nbsp;&nb=
sp; multicast source &quot;root-EID&quot; has moved to a remote LISP site.&=
nbsp; Under<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt;&nbsp;&nbsp;&nb=
sp; such circumstances LISP sends a SMR message to all receiver xTRs,<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt;&nbsp;&nbsp;&nb=
sp; prompting them to update their map cache.&nbsp; This is only possible i=
f<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt;&nbsp;&nbsp;&nb=
sp; LISP can obtain from PIM the set of all receiver RLOCS that have<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&gt;&nbsp;&nbsp;&nb=
sp; active Join state for the root-EID.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">This paragraph does=
 not make it clear if the EID that is moving is the root-EID or the receive=
r host that moves to another LISP site where there may be a new receiver-RL=
OC for head-end replication.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">The reason I say th=
at is because the way the paragraph starts, but as it continues, it is refe=
rring to the root-EID changing. And when you say &#8220;LISP sends a SMR me=
ssage&#8221; it doesn&#8217;t say if the old root-xTR
 sends it or the new root-xTR the root-EID move into does.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">So are you trying t=
o inform the receiver-xTRs to tell the new root-xTR about some new state? L=
ike for instance, start joining the (root-RLOC, G) in the underlay? If so, =
this paragraph I thought was for head-end
 replication.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">So in any event, I&=
#8217;m completely confused on (1) what event is occurring, and (2) what th=
e mechanism is and (3) why you are doing the action you are doing.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Dino<o:p></o:p></sp=
an></p>
</div>
</body>
</html>

--_000_ead4d10adfe946f3afaae63b784d301eXCHALN008ciscocom_--


From nobody Thu Jun  2 17:36:04 2016
Return-Path: <farinacci@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6BE12D0AB; Thu,  2 Jun 2016 17:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A9mApWyx72UN; Thu,  2 Jun 2016 17:35:49 -0700 (PDT)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6358112D53F; Thu,  2 Jun 2016 17:35:44 -0700 (PDT)
Received: by mail-qg0-x234.google.com with SMTP id 93so4763789qgx.2; Thu, 02 Jun 2016 17:35:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rXO83IgXUcPO+5DkjaERZf1hr4Al1XnbdTrvgY1SaiQ=; b=S801XGbS0VAklQz6s9Dg2I0SGajKK+RgWj3V1GocE/KNR6AknWr+2exry5nSCLdqOS xubYhxrXwmt7mhU4JB8ElOwhTnJrTT9kQwY9GbEQdPlsxLRG3YwuDd8q0oTA5pyz+jDl 4TWUHUczO0bmQGUl9GQE6eccHHutGOKi43N5YxBINAizSh/7NvmWKzJNPliDYIeOyeU8 0fqXDWdo6QkDN5rIHJT71reVnOyyGBLKcNkPgMjycilmDy88ENKDbWg3aj3t8IxAGmAR p5nBSbl72J0P3dj7RWgW8rCQCRugI4Z1oi4/Rd3Tnx5YAIzqJzaE7EiVqrL0xpVlKHDK +BAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rXO83IgXUcPO+5DkjaERZf1hr4Al1XnbdTrvgY1SaiQ=; b=Q1F+U3ITeNmsiUyQHoC6ULCL2VLIfm7z+/N1Xf4grnigiTkIicjitFU+xPZywPStMy 8+4UxtJsY9b10uUlLbWgUOfpym0CVaSOzw7SsfLmMwfRVir/TY6pNv/cMPN9bHROCclY 1I8EeH64v4QJsQlTKP1zG0bkgNyrBuRMA/0EPgJ2zGsn9yuILx7o6JVsXI5yXg4BZKTu +AjUuG+1X6kW4uyWAbDzhAAvfMIoniZ//7oPGJAprvP3VGIsDhq+/q2SHUln/DcT4eb3 yQf2H7UJoz4mU1GpfkFc2fDr8xzzTc82/jduo4489xLSWJQ4fjzSNFe+B6eD41f0eFeG sJOA==
X-Gm-Message-State: ALyK8tIvoRztANiMXbMDpXbj7+im2EgCZWIBasHQdpQj/87EMzusXxbZD3BijEMZ3MsO4g==
X-Received: by 10.140.38.145 with SMTP id t17mr865739qgt.10.1464914143569; Thu, 02 Jun 2016 17:35:43 -0700 (PDT)
Received: from [10.22.113.189] ([166.170.34.78]) by smtp.gmail.com with ESMTPSA id o128sm380635qkb.40.2016.06.02.17.35.42 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Jun 2016 17:35:43 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (13F69)
In-Reply-To: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com>
Date: Thu, 2 Jun 2016 20:35:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FAB6A25-739D-462D-BE0B-7768BCD04753@gmail.com>
References: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com>
To: "Jesus Arango (jearango)" <jearango@cisco.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/HQOaEkuWBuFtda5_OS9Fr0fOTwY>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "Stig Venaas \(svenaas\)" <stig@cisco.com>
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 00:36:00 -0000

> To support mobile multicast sources, the root xTR must keep track of ALL r=
eceiver RLOCs even when the corresponding receiver XTRs have not requested u=
nicast

It is better for clarity of the text. Now I will comment on the design.=20

> replication.  If the root xTR detects that the root-EID has moved to a new=
 root xTR, it sends an SMR message to all receiver xTRs, =20

You don't need SMRs. You can use Map-Notify messages from the map-server. It=
 converges better.=20

See draft-ietf-lisp-signal-free-multicast for
details. The same machinery can be used. And it is simple.=20

> prompting them to update their map cache. =20

Receiver xTRs are receiving and decapsulating packets. They are ETRs. They d=
on't have map-caches. So this doesn't make sense.=20

> This is only possible if  LISP can obtain from PIM the set of all receiver=
 RLOCS that have active Join state for the root-EID.

Well they could register to the mapping system. That is where all receiver x=
TRs can be tracked (and perhaps not used for forwarding like it is in draft-=
ietf-lisp-signal-free-multicast).=20

So try again.=20

Dino=


From nobody Thu Jun  2 18:26:45 2016
Return-Path: <jearango@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D4812D5D7; Thu,  2 Jun 2016 18:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhYfwdYmtUzO; Thu,  2 Jun 2016 18:26:41 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADA2412D5B7; Thu,  2 Jun 2016 18:26:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2269; q=dns/txt; s=iport; t=1464917201; x=1466126801; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=eqn4O8g/YpieR+wuuTBDUzoBA4OuiaO0dbwUhIxgl+Q=; b=AJ9R5oampgVNHE+N3Pi7jxVKnrVEA/JfQoRDgBhRD5bCcY+sEN4HaHHv C9xrPFXMDIAHuRZtQjIM2RSq2awQ4yYUQK/BccsAGSsJ8Ba2+LzHtlyK3 SUvCMIK5dyT3xY8vSQk9R9HbmIob1oFosGvMZreRXvgrikuXjN2bXYjoE w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgCA3FBX/4YNJK1egzqBUwauVolgg?= =?us-ascii?q?g+BeYYSAoE2OBQBAQEBAQEBZSeERQEBAQMBOj8FBwQCAQgRBAEBHwkHIREUCQg?= =?us-ascii?q?CBA4FCIgNAw8IvjwNhB8BAQEBAQEBAQEBAQEBAQEBAQEBAQEchieETYJDgWeFc?= =?us-ascii?q?AWYBTMBjCaBcoFwjTOGM4Exh2cBHjaCBxyBS26JfX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,409,1459814400"; d="scan'208";a="281175955"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Jun 2016 01:26:20 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u531QKJX010263 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 3 Jun 2016 01:26:20 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 2 Jun 2016 20:26:19 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1104.009; Thu, 2 Jun 2016 20:26:19 -0500
From: "Jesus Arango (jearango)" <jearango@cisco.com>
To: Dino Farinacci <farinacci@gmail.com>
Thread-Topic: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03
Thread-Index: AQHRvS/rP5y/rkLukEibTEvdyF5U2p/W6s5w
Date: Fri, 3 Jun 2016 01:26:19 +0000
Message-ID: <e82c19c4ebef4c32adb6752047eb6232@XCH-ALN-008.cisco.com>
References: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com> <0FAB6A25-739D-462D-BE0B-7768BCD04753@gmail.com>
In-Reply-To: <0FAB6A25-739D-462D-BE0B-7768BCD04753@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.25.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/C2AvzMKf2P-JT7e215BMx6p3mGk>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "Stig Venaas \(svenaas\)" <stig@cisco.com>
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 01:26:43 -0000

Hi Dino,

I don't think map-notifies are relevant in the context of this draft. Keep =
in mind that this draft is written for "pim-signaled" head-end replication.=
 In your "signal-free" draft, map-notifies are the correct message because =
you are tracking changes in the set of receiver RLOCS and that translates i=
nto changes in the merged RLOC set. In this draft, we are tracking changes =
in source EID location and the proper message for that is an SMR.

The receivers do have map-caches. They have a map-cache entry mapping the s=
ource EID to the RLOC of the source XTR. This is the map-cache entry that w=
e want the SMR to refresh. The creation of this map-cache was not triggered=
 by traffic. It was triggered by an RPF lookup by PIM in the receiver XTR.

Jesus

-----Original Message-----
From: Dino Farinacci [mailto:farinacci@gmail.com]=20
Sent: Thursday, June 2, 2016 5:36 PM
To: Jesus Arango (jearango) <jearango@cisco.com>
Cc: pim@ietf.org; lisp@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: Re: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03

> To support mobile multicast sources, the root xTR must keep track of=20
> ALL receiver RLOCs even when the corresponding receiver XTRs have not=20
> requested unicast

It is better for clarity of the text. Now I will comment on the design.=20

> replication.  If the root xTR detects that the root-EID has moved to a=20
> new root xTR, it sends an SMR message to all receiver xTRs,

You don't need SMRs. You can use Map-Notify messages from the map-server. I=
t converges better.=20

See draft-ietf-lisp-signal-free-multicast for details. The same machinery c=
an be used. And it is simple.=20

> prompting them to update their map cache. =20

Receiver xTRs are receiving and decapsulating packets. They are ETRs. They =
don't have map-caches. So this doesn't make sense.=20

> This is only possible if  LISP can obtain from PIM the set of all receive=
r RLOCS that have active Join state for the root-EID.

Well they could register to the mapping system. That is where all receiver =
xTRs can be tracked (and perhaps not used for forwarding like it is in draf=
t-ietf-lisp-signal-free-multicast).=20

So try again.=20

Dino


From nobody Thu Jun  2 19:47:04 2016
Return-Path: <farinacci@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F8C12D131; Thu,  2 Jun 2016 19:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RC_8Yyg57IeP; Thu,  2 Jun 2016 19:47:00 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 414D9128874; Thu,  2 Jun 2016 19:47:00 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id n63so48231911qkf.0; Thu, 02 Jun 2016 19:47:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=laie6fjvCJldzf8nSEdeABaEK1WDZaouDHRbHRnePYs=; b=g1IiB+3YQSd3FFovxxOfcrExdcvQpSK30038Bnd7Sc5lSvFoP8KvjzlTKShVjegn8A GZLgayxIu83p/b7L4WnsbcnprlehoAhTdz4x/Cbqp90GLMDYfkDuwIm5U3NgydhaurEe gf+nFdt4juIir6WbGro6vGwafdYUhyWgxF3N8fVdquz7cYXD3kf2Rp5JEhMK9UIOmXZ0 WQi6T70O5Kuk9vRH2ZoGyT4JQ4jJRgWGw1Yoa0lcR7SP34PqXSfkRbv5NMOUEp7nZS7i BNdEuSeqWqXZvsHisqU8nDH6aTt7J0viVVkfQfz2BRw/1djOGlDA+LUx3q38O+03XjUP mNqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=laie6fjvCJldzf8nSEdeABaEK1WDZaouDHRbHRnePYs=; b=aQR/ef1wfeg5/HcEF1sbvVvXS6N63uYJQpir58dS8yKUmbHa/zQS6k/PnVWkQqWTju Jn9+/EvmUmjWh9kU2H3wMep+JiLz/eUymYMX2Keurw5WKJwAXhVFI5ZMyZ1rNJtsQ6Rl sPs11obmlY7ZrcP2vU8JB+CDtM+L/YSNl9v2GgRBC6pgjAmrw86O8EZxeuRN5qOQevIn 0/Im8OZD06V9a+X90w8iEw8q9OkNuPgC36TJlA9xKQ6qZNRJs6DwwYCXMYCs1b++wIV8 kt2O+6juewMKx9t2COA/bBi5cDyh3dmgrCj8COPuoQabL5lS5STcZ3ofTPl8dHcBPD8V vUAQ==
X-Gm-Message-State: ALyK8tL3s7pUDDKq3xsEFFzg4UDwPnzkQnxpNbik+PmbBaoem8K6nIO90N/lz6YInBjqhw==
X-Received: by 10.55.90.130 with SMTP id o124mr1219224qkb.178.1464922019365; Thu, 02 Jun 2016 19:46:59 -0700 (PDT)
Received: from [10.22.113.189] ([166.170.34.78]) by smtp.gmail.com with ESMTPSA id h66sm516129qgh.15.2016.06.02.19.46.57 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Jun 2016 19:46:57 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (13F69)
In-Reply-To: <e82c19c4ebef4c32adb6752047eb6232@XCH-ALN-008.cisco.com>
Date: Thu, 2 Jun 2016 22:46:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <76C8DE6E-7E98-45BA-96FC-E25ABFF4EFDE@gmail.com>
References: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com> <0FAB6A25-739D-462D-BE0B-7768BCD04753@gmail.com> <e82c19c4ebef4c32adb6752047eb6232@XCH-ALN-008.cisco.com>
To: "Jesus Arango (jearango)" <jearango@cisco.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/K7EvmNxq_IKyk7a-31C-Z4Ruu0g>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "Stig Venaas \(svenaas\)" <stig@cisco.com>
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 02:47:02 -0000

> I don't think map-notifies are relevant in the context of this draft. Keep=
 in mind that this draft is written for "pim-signaled" head-end replication.=
 In your "signal-free" draft, map-notifies are the correct message because y=
ou are tracking changes in the set of receiver RLOCS and that translates int=
o changes in the merged RLOC set. In this draft, we are tracking changes in s=
ource EID location and the proper message for that is an SMR.

I was thinking of using Map-Notifies in this application not in the signal-f=
ree one.=20

What you do is have the root-xTR register as  a receiver-xTR so when a move o=
ccurs the new root-xTR changes which causes the map-server to trigger a Map-=
Notify to each RLOC in the RLIC-set  because there was an RLOC-set change.=20=


> The receivers do have map-caches. They

In this data forwarding direction, this is an ETR. ETRs have database-entrie=
s which are registered. Used for decapsulation.=20

Mao-caches are used for encapsulation. There is no encapsulation in these re=
ceiver-ETRs when data flows from a multicast source to the receivers the rec=
eiver-ETR supports.=20

> have a map-cache entry mapping the source EID to the RLOC of the source XT=
R.

That is a map-cache entry in the root-ITR not in the ETRs.=20

> This is the map-cache entry that we want the SMR to refresh. The creation o=
f this

That is why this is backwards.=20

> map-cache was not triggered by traffic. It was triggered by an RPF lookup b=
y PIM in the receiver XTR.

Understand. But it should be called another data structure. Like an RPF data=
 structure, like a RIB is used in normal native routing.=20

In any event, if you don't clear up this text, it will be hard for anyone to=
 understand this.=20

Dino=


From nobody Mon Jun  6 20:13:47 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1657612D760; Mon,  6 Jun 2016 20:13:45 -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: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160607031345.13686.20157.idtracker@ietfa.amsl.com>
Date: Mon, 06 Jun 2016 20:13:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/g8MrG07ojyEPl9cZSZanJ8_NPxk>
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-dr-improvement-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2016 03:13:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocols for IP Multicast of the IETF.

        Title           : PIM DR Improvement
        Authors         : Zheng(Sandy) Zhang
                          Fangwei Hu
                          BenChong Xu
	Filename        : draft-ietf-pim-dr-improvement-01.txt
	Pages           : 8
	Date            : 2016-06-06

Abstract:
   PIM is worldly deployed multicast protocol.  This document will
   improve the stability of PIM protocol, decrease the lost of multicast
   packets when the PIM DR (Designed Router) is down.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-pim-dr-improvement-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pim-dr-improvement-01


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

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


From nobody Tue Jun  7 23:47:31 2016
Return-Path: <jearango@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A731912D7F4; Tue,  7 Jun 2016 23:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mZFdO3pYaI0N; Tue,  7 Jun 2016 23:47:26 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D79A12D18E; Tue,  7 Jun 2016 23:47:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2375; q=dns/txt; s=iport; t=1465368446; x=1466578046; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ZbQRF8zJYcl0eo2adNx2o+AAk+eEqRmhOnUREZZYPRA=; b=g7cTTYq3Ky+pmyIOsmzKeFdPiSNwut7wgK3t7f8TxcdcLDfSkhsvrFzM IJSyzFxl/cEI5YINHcPfaZ8jnschwsyyckr+bFaGCNMAoVa9F4BDhJPXw AA812RKDoxqoit2WSdk9LdZLWcvt3QLKBhod13Z+rsqlE0304exp+Zzxx I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D1AQDpvldX/4YNJK1dgz6BUwavB4lwg?= =?us-ascii?q?g+BeYYTAoE+OBQBAQEBAQEBZSeERQEBAQMBOj8FBwQCAQgRBAEBHwkHIREUCQg?= =?us-ascii?q?CBA4FCIgNAw8IuSUNhAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEchieETYJDgWeFc?= =?us-ascii?q?AWYGzQBjCuBc48mh3WHawEeNoIHHIFLbokQfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.26,437,1459814400"; d="scan'208";a="283106783"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Jun 2016 06:47:25 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u586lPrX022639 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 Jun 2016 06:47:25 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 8 Jun 2016 01:47:24 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1104.009; Wed, 8 Jun 2016 01:47:24 -0500
From: "Jesus Arango (jearango)" <jearango@cisco.com>
To: Dino Farinacci <farinacci@gmail.com>
Thread-Topic: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03
Thread-Index: AQHRvS/rP5y/rkLukEibTEvdyF5U2p/W6s5wgABzBgCAB8nhcA==
Date: Wed, 8 Jun 2016 06:47:24 +0000
Message-ID: <0f78a5f449594ad5ba5e2c7c8deee2d6@XCH-ALN-008.cisco.com>
References: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com> <0FAB6A25-739D-462D-BE0B-7768BCD04753@gmail.com> <e82c19c4ebef4c32adb6752047eb6232@XCH-ALN-008.cisco.com> <76C8DE6E-7E98-45BA-96FC-E25ABFF4EFDE@gmail.com>
In-Reply-To: <76C8DE6E-7E98-45BA-96FC-E25ABFF4EFDE@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.67.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/J59YlxwjoVch4nHLJxvpt5rel4s>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "Stig Venaas \(svenaas\)" <stig@cisco.com>
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2016 06:47:28 -0000

FYI,

I am collaborating with Dino on his comments. We agreed to do some changes =
and are actively working on them. I will share the changes and publish a ne=
w draft version once we reach an agreement on the exact wording to use.

Thanks
Jesus


-----Original Message-----
From: Dino Farinacci [mailto:farinacci@gmail.com]=20
Sent: Thursday, June 2, 2016 7:47 PM
To: Jesus Arango (jearango) <jearango@cisco.com>
Cc: pim@ietf.org; lisp@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: Re: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03

> I don't think map-notifies are relevant in the context of this draft. Kee=
p in mind that this draft is written for "pim-signaled" head-end replicatio=
n. In your "signal-free" draft, map-notifies are the correct message becaus=
e you are tracking changes in the set of receiver RLOCS and that translates=
 into changes in the merged RLOC set. In this draft, we are tracking change=
s in source EID location and the proper message for that is an SMR.

I was thinking of using Map-Notifies in this application not in the signal-=
free one.=20

What you do is have the root-xTR register as  a receiver-xTR so when a move=
 occurs the new root-xTR changes which causes the map-server to trigger a M=
ap-Notify to each RLOC in the RLIC-set  because there was an RLOC-set chang=
e.=20

> The receivers do have map-caches. They

In this data forwarding direction, this is an ETR. ETRs have database-entri=
es which are registered. Used for decapsulation.=20

Mao-caches are used for encapsulation. There is no encapsulation in these r=
eceiver-ETRs when data flows from a multicast source to the receivers the r=
eceiver-ETR supports.=20

> have a map-cache entry mapping the source EID to the RLOC of the source X=
TR.

That is a map-cache entry in the root-ITR not in the ETRs.=20

> This is the map-cache entry that we want the SMR to refresh. The creation=
 of this

That is why this is backwards.=20

> map-cache was not triggered by traffic. It was triggered by an RPF lookup=
 by PIM in the receiver XTR.

Understand. But it should be called another data structure. Like an RPF dat=
a structure, like a RIB is used in normal native routing.=20

In any event, if you don't clear up this text, it will be hard for anyone t=
o understand this.=20

Dino


From nobody Wed Jun  8 18:40:04 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFE912D8F3; Wed,  8 Jun 2016 18:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level: 
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 EdocjbjSzXBI; Wed,  8 Jun 2016 18:39:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7FD512D7AB; Wed,  8 Jun 2016 18:39:44 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BFF70B80B13; Wed,  8 Jun 2016 18:39:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160609013944.BFF70B80B13@rfc-editor.org>
Date: Wed,  8 Jun 2016 18:39:44 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/o5HUZ15etMvfRafenLACn7ugQPM>
Cc: drafts-update-ref@iana.org, pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] RFC 7887 on Hierarchical Join/Prune Attributes
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2016 01:39:55 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7887

        Title:      Hierarchical Join/Prune Attributes 
        Author:     S. Venaas, J. Arango, I. Kouvelas
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2016
        Mailbox:    stig@cisco.com, 
                    jearango@cisco.com, 
                    kouvelas@arista.com
        Pages:      8
        Characters: 17207
        Updates:    RFC 5384

        I-D Tag:    draft-ietf-pim-hierarchicaljoinattr-08.txt

        URL:        https://www.rfc-editor.org/info/rfc7887

        DOI:        http://dx.doi.org/10.17487/RFC7887

This document defines a hierarchical method of encoding Join/Prune
attributes that provides a more efficient encoding when the same
attribute values need to be specified for multiple sources in a PIM
Join/Prune message.  This document updates RFC 5384 by renaming the
encoding type registry specified there.

This document is a product of the Protocols for IP Multicast Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Tue Jun 14 12:21:00 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A3B12D92B; Tue, 14 Jun 2016 12:20:54 -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: 6.22.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160614192054.19195.36403.idtracker@ietfa.amsl.com>
Date: Tue, 14 Jun 2016 12:20:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/klzQNBZDXHLufQ7N4fA5H29JdqE>
Cc: pim@ietf.org
Subject: [pim] I-D Action: draft-ietf-pim-join-attributes-for-lisp-04.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2016 19:20:54 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocols for IP Multicast of the IETF.

        Title           : PIM Join Attributes for LISP Environments
        Authors         : Jesus Arango
                          Stig Venaas
                          Isidor Kouvelas
                          Dino Farinacci
	Filename        : draft-ietf-pim-join-attributes-for-lisp-04.txt
	Pages           : 8
	Date            : 2016-06-14

Abstract:
   This document defines two PIM Join/Prune attributes that support the
   construction of multicast distribution trees where the root and
   receivers are located in different LISP sites.  These attributes
   allow the receiver site to select between unicast and multicast
   underlay transport and to convey the receiver ETR's RLOC address to
   the control plane of the root ITR.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-pim-join-attributes-for-lisp-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pim-join-attributes-for-lisp-04


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

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


From nobody Tue Jun 14 12:24:11 2016
Return-Path: <jearango@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6C012D922; Tue, 14 Jun 2016 12:24:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OEYJSiR87DLe; Tue, 14 Jun 2016 12:24:08 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 939BA12D91D; Tue, 14 Jun 2016 12:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2889; q=dns/txt; s=iport; t=1465932248; x=1467141848; h=from:to:cc:subject:date:message-id:references: content-transfer-encoding:mime-version; bh=Ej7MCDqvNpZrYYh6SIokNM0DUc+5BVDIFOFvc4/jJCo=; b=FWY0yoBdv17fe65ZCW94ZClb38ige1q+r4kaNtCEXg6pRhyW/3JnYm1A Ey4AGpYRseZ3we4KGN3a8ocQx9/1AKlZ+kYr2VqFD6hnNrEJKuPYheaqW KQb/+EaB5lhFICVXop/zxX1R9y7VKRij/eh3K5uTTA5ftH7hy7Fnjq5ci 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ALAgBSWWBX/4gNJK1dgz5WfQavMolzg?= =?us-ascii?q?g+BeSKFdQKBNDgUAQEBAQEBAWUnhEsBAQEDATo/BQcEAgEIEQQBAR8JByERFAk?= =?us-ascii?q?IAgQOBQiIDgMPCA65Mg2DcwEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhieETYJDg?= =?us-ascii?q?WeFcQWYLzQBhgSGKoFzjymIB4dsAR42ggccgUtuiQl/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,471,1459814400"; d="scan'208";a="117879403"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Jun 2016 19:24:07 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u5EJO7Px012442 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 14 Jun 2016 19:24:07 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 14 Jun 2016 14:24:06 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1104.009; Tue, 14 Jun 2016 14:24:06 -0500
From: "Jesus Arango (jearango)" <jearango@cisco.com>
To: Dino Farinacci <farinacci@gmail.com>
Thread-Topic: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03
Thread-Index: AQHRvS/rP5y/rkLukEibTEvdyF5U2p/W6s5wgABzBgCAB8nhcIAKQhBA
Date: Tue, 14 Jun 2016 19:24:06 +0000
Message-ID: <fcb5c3cafbce4c6ebe009cc8dc312294@XCH-ALN-008.cisco.com>
References: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com> <0FAB6A25-739D-462D-BE0B-7768BCD04753@gmail.com> <e82c19c4ebef4c32adb6752047eb6232@XCH-ALN-008.cisco.com> <76C8DE6E-7E98-45BA-96FC-E25ABFF4EFDE@gmail.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.122.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/ZALoUwm_sCOx37zyRSzDfKrlys4>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "Stig Venaas \(svenaas\)" <stig@cisco.com>
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2016 19:24:10 -0000

FYI,

A new version has been uploaded with all the revisions that were brought up=
 during the last-call. Here is the new version:

https://tools.ietf.org/html/draft-ietf-pim-join-attributes-for-lisp-04

Jesus

-----Original Message-----
From: Jesus Arango (jearango)=20
Sent: Tuesday, June 7, 2016 11:47 PM
To: 'Dino Farinacci' <farinacci@gmail.com>
Cc: pim@ietf.org; lisp@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: RE: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03

FYI,

I am collaborating with Dino on his comments. We agreed to do some changes =
and are actively working on them. I will share the changes and publish a ne=
w draft version once we reach an agreement on the exact wording to use.

Thanks
Jesus


-----Original Message-----
From: Dino Farinacci [mailto:farinacci@gmail.com]=20
Sent: Thursday, June 2, 2016 7:47 PM
To: Jesus Arango (jearango) <jearango@cisco.com>
Cc: pim@ietf.org; lisp@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: Re: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03

> I don't think map-notifies are relevant in the context of this draft. Kee=
p in mind that this draft is written for "pim-signaled" head-end replicatio=
n. In your "signal-free" draft, map-notifies are the correct message becaus=
e you are tracking changes in the set of receiver RLOCS and that translates=
 into changes in the merged RLOC set. In this draft, we are tracking change=
s in source EID location and the proper message for that is an SMR.

I was thinking of using Map-Notifies in this application not in the signal-=
free one.=20

What you do is have the root-xTR register as  a receiver-xTR so when a move=
 occurs the new root-xTR changes which causes the map-server to trigger a M=
ap-Notify to each RLOC in the RLIC-set  because there was an RLOC-set chang=
e.=20

> The receivers do have map-caches. They

In this data forwarding direction, this is an ETR. ETRs have database-entri=
es which are registered. Used for decapsulation.=20

Mao-caches are used for encapsulation. There is no encapsulation in these r=
eceiver-ETRs when data flows from a multicast source to the receivers the r=
eceiver-ETR supports.=20

> have a map-cache entry mapping the source EID to the RLOC of the source X=
TR.

That is a map-cache entry in the root-ITR not in the ETRs.=20

> This is the map-cache entry that we want the SMR to refresh. The creation=
 of this

That is why this is backwards.=20

> map-cache was not triggered by traffic. It was triggered by an RPF lookup=
 by PIM in the receiver XTR.

Understand. But it should be called another data structure. Like an RPF dat=
a structure, like a RIB is used in normal native routing.=20

In any event, if you don't clear up this text, it will be hard for anyone t=
o understand this.=20

Dino


From nobody Tue Jun 14 17:27:02 2016
Return-Path: <Michael.McBride@huawei.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ACDC12DA5D; Tue, 14 Jun 2016 17:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level: 
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Cu40wTpUGR2B; Tue, 14 Jun 2016 17:26:59 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50DDA12DA5C; Tue, 14 Jun 2016 17:26:58 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CQU93127; Wed, 15 Jun 2016 00:26:56 +0000 (GMT)
Received: from DFWEML703-CAH.china.huawei.com (10.193.5.177) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 15 Jun 2016 01:26:54 +0100
Received: from DFWEML501-MBX.china.huawei.com ([10.193.5.178]) by DFWEML703-CAH.china.huawei.com ([10.193.5.177]) with mapi id 14.03.0235.001; Tue, 14 Jun 2016 17:26:48 -0700
From: Michael McBride <Michael.McBride@huawei.com>
To: "Jesus Arango (jearango)" <jearango@cisco.com>, Dino Farinacci <farinacci@gmail.com>
Thread-Topic: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
Thread-Index: AdG9Jym5/S5pdX1PTh6RhuAiNX6jXp/W6s5wgABzBgCAB8nhcIAKQhBAn9Z/asA=
Date: Wed, 15 Jun 2016 00:26:47 +0000
Message-ID: <8CCB28152EA2E14A96BBEDC15823481A09E9A57E@dfweml501-mbx>
References: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com> <0FAB6A25-739D-462D-BE0B-7768BCD04753@gmail.com> <e82c19c4ebef4c32adb6752047eb6232@XCH-ALN-008.cisco.com> <76C8DE6E-7E98-45BA-96FC-E25ABFF4EFDE@gmail.com> <fcb5c3cafbce4c6ebe009cc8dc312294@XCH-ALN-008.cisco.com>
In-Reply-To: <fcb5c3cafbce4c6ebe009cc8dc312294@XCH-ALN-008.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.144.91]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.5760A0D0.00CB, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6ed223868ffd49680c2c2e2e693098a2
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/hhc9ofj3ux_N_wtNVIxLjrUMdng>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "Stig Venaas \(svenaas\)" <stig@cisco.com>
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2016 00:27:01 -0000

Hi Jesus,

Have all comments (Dino's) been addressed in this rev? If so we will forwar=
d the draft to Alvaro (iesg). Otherwise we will wait until everyone is happ=
y.

thanks,
mike

-----Original Message-----
From: pim [mailto:pim-bounces@ietf.org] On Behalf Of Jesus Arango (jearango=
)
Sent: Tuesday, June 14, 2016 12:24 PM
To: Dino Farinacci
Cc: lisp@ietf.org; pim@ietf.org; Stig Venaas (svenaas)
Subject: Re: [pim] [lisp] WGLC draft-ietf-pim-join-attributes-for-lisp-03

FYI,

A new version has been uploaded with all the revisions that were brought up=
 during the last-call. Here is the new version:

https://tools.ietf.org/html/draft-ietf-pim-join-attributes-for-lisp-04

Jesus

-----Original Message-----
From: Jesus Arango (jearango)=20
Sent: Tuesday, June 7, 2016 11:47 PM
To: 'Dino Farinacci' <farinacci@gmail.com>
Cc: pim@ietf.org; lisp@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: RE: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03

FYI,

I am collaborating with Dino on his comments. We agreed to do some changes =
and are actively working on them. I will share the changes and publish a ne=
w draft version once we reach an agreement on the exact wording to use.

Thanks
Jesus


-----Original Message-----
From: Dino Farinacci [mailto:farinacci@gmail.com]=20
Sent: Thursday, June 2, 2016 7:47 PM
To: Jesus Arango (jearango) <jearango@cisco.com>
Cc: pim@ietf.org; lisp@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: Re: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03

> I don't think map-notifies are relevant in the context of this draft. Kee=
p in mind that this draft is written for "pim-signaled" head-end replicatio=
n. In your "signal-free" draft, map-notifies are the correct message becaus=
e you are tracking changes in the set of receiver RLOCS and that translates=
 into changes in the merged RLOC set. In this draft, we are tracking change=
s in source EID location and the proper message for that is an SMR.

I was thinking of using Map-Notifies in this application not in the signal-=
free one.=20

What you do is have the root-xTR register as  a receiver-xTR so when a move=
 occurs the new root-xTR changes which causes the map-server to trigger a M=
ap-Notify to each RLOC in the RLIC-set  because there was an RLOC-set chang=
e.=20

> The receivers do have map-caches. They

In this data forwarding direction, this is an ETR. ETRs have database-entri=
es which are registered. Used for decapsulation.=20

Mao-caches are used for encapsulation. There is no encapsulation in these r=
eceiver-ETRs when data flows from a multicast source to the receivers the r=
eceiver-ETR supports.=20

> have a map-cache entry mapping the source EID to the RLOC of the source X=
TR.

That is a map-cache entry in the root-ITR not in the ETRs.=20

> This is the map-cache entry that we want the SMR to refresh. The creation=
 of this

That is why this is backwards.=20

> map-cache was not triggered by traffic. It was triggered by an RPF lookup=
 by PIM in the receiver XTR.

Understand. But it should be called another data structure. Like an RPF dat=
a structure, like a RIB is used in normal native routing.=20

In any event, if you don't clear up this text, it will be hard for anyone t=
o understand this.=20

Dino

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


From nobody Tue Jun 14 17:30:11 2016
Return-Path: <jearango@cisco.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7AEC12DA4D; Tue, 14 Jun 2016 17:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gXnxOdbcslNe; Tue, 14 Jun 2016 17:30:07 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0A2F12DA5C; Tue, 14 Jun 2016 17:30:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4007; q=dns/txt; s=iport; t=1465950606; x=1467160206; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=geIytB/TYSzr6TV54WoBEelhYaREmeUcoxO3Jg8dA/o=; b=cPh5WUtRRbiXIRZLcbwBZzUJfMXwHrpVOPIQ3pBZC4P2B909P+x9sq8T gVME+0QyRMxUuk7fb4PKieJb6kNSTddg2UJDZ4ad+D6j8uxGgDS/WIbce bgrhmPhQ6CwSqY71K3ilnhu/mWwHkggktmjxx5Z6FwZcctA8oBfp4yKv/ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AfAgA2oGBX/49dJa1dgz5WfQavMIwCg?= =?us-ascii?q?XkXC4V1AoE1OBQBAQEBAQEBZSeESwEBAQMBAQEBNzQLBQcEAgEIEQQBAR8JByE?= =?us-ascii?q?GCxQJCAIEAQ0FCIgOAw8IDrleDYNzAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWGJ?= =?us-ascii?q?4RNgkOBZ4VxBZgvNAGGBIYqgXOPKYgHh2wBHjaCBxyBS26JCX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,473,1459814400"; d="scan'208";a="283830692"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Jun 2016 00:30:06 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u5F0U53C000567 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 Jun 2016 00:30:06 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 14 Jun 2016 19:30:05 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1104.009; Tue, 14 Jun 2016 19:30:05 -0500
From: "Jesus Arango (jearango)" <jearango@cisco.com>
To: Michael McBride <Michael.McBride@huawei.com>, Dino Farinacci <farinacci@gmail.com>
Thread-Topic: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
Thread-Index: AQHRxpygmemjggFTX0OHTWYdk2xu8Z/prJzw
Date: Wed, 15 Jun 2016 00:30:05 +0000
Message-ID: <5816be226b114ede84672f2786b1adaa@XCH-ALN-008.cisco.com>
References: <ead4d10adfe946f3afaae63b784d301e@XCH-ALN-008.cisco.com> <0FAB6A25-739D-462D-BE0B-7768BCD04753@gmail.com> <e82c19c4ebef4c32adb6752047eb6232@XCH-ALN-008.cisco.com> <76C8DE6E-7E98-45BA-96FC-E25ABFF4EFDE@gmail.com> <fcb5c3cafbce4c6ebe009cc8dc312294@XCH-ALN-008.cisco.com> <8CCB28152EA2E14A96BBEDC15823481A09E9A57E@dfweml501-mbx>
In-Reply-To: <8CCB28152EA2E14A96BBEDC15823481A09E9A57E@dfweml501-mbx>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.122.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/TqFzzna1hTtXJI3hEkY2aqSoulM>
Cc: "lisp@ietf.org" <lisp@ietf.org>, "pim@ietf.org" <pim@ietf.org>, "Stig Venaas \(svenaas\)" <stig@cisco.com>
Subject: Re: [pim] [lisp]  WGLC draft-ietf-pim-join-attributes-for-lisp-03
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2016 00:30:08 -0000

Hi Mike,

Yes, all comments were addressed. I received approval from Dino and from al=
l other authors.

Thank you
Jesus

-----Original Message-----
From: Michael McBride [mailto:Michael.McBride@huawei.com]=20
Sent: Tuesday, June 14, 2016 5:27 PM
To: Jesus Arango (jearango) <jearango@cisco.com>; Dino Farinacci <farinacci=
@gmail.com>
Cc: lisp@ietf.org; pim@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: RE: [pim] [lisp] WGLC draft-ietf-pim-join-attributes-for-lisp-03

Hi Jesus,

Have all comments (Dino's) been addressed in this rev? If so we will forwar=
d the draft to Alvaro (iesg). Otherwise we will wait until everyone is happ=
y.

thanks,
mike

-----Original Message-----
From: pim [mailto:pim-bounces@ietf.org] On Behalf Of Jesus Arango (jearango=
)
Sent: Tuesday, June 14, 2016 12:24 PM
To: Dino Farinacci
Cc: lisp@ietf.org; pim@ietf.org; Stig Venaas (svenaas)
Subject: Re: [pim] [lisp] WGLC draft-ietf-pim-join-attributes-for-lisp-03

FYI,

A new version has been uploaded with all the revisions that were brought up=
 during the last-call. Here is the new version:

https://tools.ietf.org/html/draft-ietf-pim-join-attributes-for-lisp-04

Jesus

-----Original Message-----
From: Jesus Arango (jearango)=20
Sent: Tuesday, June 7, 2016 11:47 PM
To: 'Dino Farinacci' <farinacci@gmail.com>
Cc: pim@ietf.org; lisp@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: RE: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03

FYI,

I am collaborating with Dino on his comments. We agreed to do some changes =
and are actively working on them. I will share the changes and publish a ne=
w draft version once we reach an agreement on the exact wording to use.

Thanks
Jesus


-----Original Message-----
From: Dino Farinacci [mailto:farinacci@gmail.com]=20
Sent: Thursday, June 2, 2016 7:47 PM
To: Jesus Arango (jearango) <jearango@cisco.com>
Cc: pim@ietf.org; lisp@ietf.org; Stig Venaas (svenaas) <stig@cisco.com>
Subject: Re: [lisp] [pim] WGLC draft-ietf-pim-join-attributes-for-lisp-03

> I don't think map-notifies are relevant in the context of this draft. Kee=
p in mind that this draft is written for "pim-signaled" head-end replicatio=
n. In your "signal-free" draft, map-notifies are the correct message becaus=
e you are tracking changes in the set of receiver RLOCS and that translates=
 into changes in the merged RLOC set. In this draft, we are tracking change=
s in source EID location and the proper message for that is an SMR.

I was thinking of using Map-Notifies in this application not in the signal-=
free one.=20

What you do is have the root-xTR register as  a receiver-xTR so when a move=
 occurs the new root-xTR changes which causes the map-server to trigger a M=
ap-Notify to each RLOC in the RLIC-set  because there was an RLOC-set chang=
e.=20

> The receivers do have map-caches. They

In this data forwarding direction, this is an ETR. ETRs have database-entri=
es which are registered. Used for decapsulation.=20

Mao-caches are used for encapsulation. There is no encapsulation in these r=
eceiver-ETRs when data flows from a multicast source to the receivers the r=
eceiver-ETR supports.=20

> have a map-cache entry mapping the source EID to the RLOC of the source X=
TR.

That is a map-cache entry in the root-ITR not in the ETRs.=20

> This is the map-cache entry that we want the SMR to refresh. The creation=
 of this

That is why this is backwards.=20

> map-cache was not triggered by traffic. It was triggered by an RPF lookup=
 by PIM in the receiver XTR.

Understand. But it should be called another data structure. Like an RPF dat=
a structure, like a RIB is used in normal native routing.=20

In any event, if you don't clear up this text, it will be hard for anyone t=
o understand this.=20

Dino

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


From nobody Wed Jun 15 15:22:08 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8F7512DC1E; Wed, 15 Jun 2016 15:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level: 
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 yRX2b9Lxd_Is; Wed, 15 Jun 2016 15:21:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAD4712DC15; Wed, 15 Jun 2016 15:21:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B113CB812B9; Wed, 15 Jun 2016 15:21:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160615222149.B113CB812B9@rfc-editor.org>
Date: Wed, 15 Jun 2016 15:21:49 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/YfkmJwKs5Ig1-dLymbWYh5Fv0tw>
Cc: drafts-update-ref@iana.org, pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] RFC 7891 on Explicit Reverse Path Forwarding (RPF) Vector
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2016 22:21:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7891

        Title:      Explicit Reverse Path Forwarding (RPF) Vector 
        Author:     J. Asghar, IJ. Wijnands, Ed.,
                    S. Krishnaswamy, A. Karan, V. Arya
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2016
        Mailbox:    jasghar@cisco.com, 
                    ice@cisco.com, 
                    sowkrish@cisco.com,
                    apoorva@cisco.com, 
                    varya@directv.com
        Pages:      9
        Characters: 19067
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pim-explicit-rpf-vector-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7891

        DOI:        http://dx.doi.org/10.17487/RFC7891

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 Rendezvous Point 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,
thus bypassing the unicast route lookup.

This document is a product of the Protocols for IP Multicast Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nlndipi@hotmail.com  Wed Jun 15 01:44:04 2016
Return-Path: <nlndipi@hotmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1360912D0CB for <pim@ietfa.amsl.com>; Wed, 15 Jun 2016 01:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, LONG_HEX_URI=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgueA-il6eF4 for <pim@ietfa.amsl.com>; Wed, 15 Jun 2016 01:44:02 -0700 (PDT)
Received: from COL004-OMC3S14.hotmail.com (col004-omc3s14.hotmail.com [65.55.34.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F8B112B04B for <pim@ietf.org>; Wed, 15 Jun 2016 01:44:02 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com ([65.55.34.135]) by COL004-OMC3S14.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 15 Jun 2016 01:44:01 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=1YjoqgeFihYka3bbPeKn2H4ysWPx5LEl80lf/DvMdls=; b=rosO7yyO9z/jbcM3GD+dJBc+BULfP+fnQCcLYiVSCzeFXzBsPOAV7atNxzpybZDzK1VdJDPjHo2/OxtbocYrpEvrpy+tADS+U7txtmPfi33oeuim/GI8zGTuGxRw5ffKpClfpuUWR3iZDoQXHOhOi9cfbmkVn2Q7aLxPk28GMt5BmH5h82QOh0p8K5mKPhK+x7dwY/86w9GQDwth/N5LTE58/I4UUlj5R+OO1cqoIljSxr6marEvAaewWGxNT+7liBamv8hxZxC5yMkYwsaczvA41yxWrGM723/5AmmSQnm7o0jisTTv1tZVJgtFSgupPU2jQVrmA8BDkFzaQm8O+w==
Received: from CY1NAM02FT033.eop-nam02.prod.protection.outlook.com (10.152.74.53) by CY1NAM02HT059.eop-nam02.prod.protection.outlook.com (10.152.75.88) with Microsoft SMTP Server (TLS) id 15.1.517.7; Wed, 15 Jun 2016 08:44:00 +0000
Received: from DM3PR19MB0667.namprd19.prod.outlook.com (10.152.74.60) by CY1NAM02FT033.mail.protection.outlook.com (10.152.75.179) with Microsoft SMTP Server (TLS) id 15.1.517.7 via Frontend Transport; Wed, 15 Jun 2016 08:43:59 +0000
Received: from DM3PR19MB0667.namprd19.prod.outlook.com ([10.164.249.139]) by DM3PR19MB0667.namprd19.prod.outlook.com ([10.164.249.139]) with mapi id 15.01.0517.014; Wed, 15 Jun 2016 08:43:59 +0000
From: ali rezaee <nlndipi@hotmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: PIM SSM(Source Specific Multicast)
Thread-Index: AQHRxuGSx96+Gf+bpUaOXKGRDS4l6g==
Date: Wed, 15 Jun 2016 08:43:59 +0000
Message-ID: <DM3PR19MB0667B3C06ABF6A12251E4EA9B7550@DM3PR19MB0667.namprd19.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=softfail (sender IP is 25.152.74.60) smtp.mailfrom=hotmail.com; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=fail action=none header.from=hotmail.com;
received-spf: SoftFail (protection.outlook.com: domain of transitioning hotmail.com discourages use of 25.152.74.60 as permitted sender)
x-tmn: [GeyyuniVHGq3kngrSLqd6CWG2EAVDG94]
x-eopattributedmessage: 0
x-forefront-antispam-report: CIP:25.152.74.60; IPV:NLI; CTRY:GB; EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1NAM02HT059; H:DM3PR19MB0667.namprd19.prod.outlook.com; FPR:; SPF:None;  CAT:NONE; LANG:en; CAT:NONE; 
x-ms-office365-filtering-correlation-id: f24eaacb-a391-4c10-8e78-08d394f931da
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(1601124038)(5061506196)(5061507196)(1603103041)(1601125047); SRVR:CY1NAM02HT059; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:CY1NAM02HT059; BCL:0; PCL:0; RULEID:; SRVR:CY1NAM02HT059; 
x-forefront-prvs: 09749A275C
Content-Type: multipart/alternative; boundary="_000_DM3PR19MB0667B3C06ABF6A12251E4EA9B7550DM3PR19MB0667namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jun 2016 08:43:59.3055 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1NAM02HT059
X-OriginalArrivalTime: 15 Jun 2016 08:44:01.0893 (UTC) FILETIME=[10E6E150:01D1C6E2]
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/R3nWw6yt0jKoQwUmCCAUBLreAmw>
X-Mailman-Approved-At: Tue, 21 Jun 2016 13:40:49 -0700
Subject: [pim] PIM SSM(Source Specific Multicast)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2016 06:07:22 -0000

--_000_DM3PR19MB0667B3C06ABF6A12251E4EA9B7550DM3PR19MB0667namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

I've been using your software for PIM-SM and I was wondering if it also sup=
ports PIM-SSM. The document at http://troglobit.github.io/pimd.html says th=
at its a PIM-SM/SSM daemon; but as of now, I haven't seen any manual on how=
 to make that work. The configuration manual at https://github.com/troglobi=
t/pimd/blob/master/pimd.conf has all the information about sparse-mode but =
nothing on SSM.

Does it support SSM?

If yes, then does it have any specific configuration options I should know =
about?

Thanks,

Ali Rezaee

[https://avatars0.githubusercontent.com/u/183517?v=3D3&s=3D400]<https://git=
hub.com/troglobit/pimd/blob/master/pimd.conf>

troglobit/pimd<https://github.com/troglobit/pimd/blob/master/pimd.conf>
github.com
pimd - The original PIM-SM multicast routing daemon.


[https://camo.githubusercontent.com/365986a132ccd6a44c23a9169022c0b5c890c38=
7/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626=
f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67]<http://trogl=
obit.github.io/pimd.html>

Pimd | the Original PIM-SM Daemon - Troglobit<http://troglobit.github.io/pi=
md.html>
troglobit.github.io
Pimd | the Original PIM-SM Daemon Nov 15th, 2015 7:26 pm pimd is a lightwei=
ght standalone PIM-SM/SSM v2 multicast routing daemon. It is the original .=
..



--_000_DM3PR19MB0667B3C06ABF6A12251E4EA9B7550DM3PR19MB0667namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;back=
ground-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hello,</p>
<p>I've been using your software for PIM-SM and I was wondering if it also =
supports PIM-SSM. The document at&nbsp;<a href=3D"http://troglobit.github.i=
o/pimd.html" class=3D"OWAAutoLink" id=3D"LPlnk270053">http://troglobit.gith=
ub.io/pimd.html</a>&nbsp;says that its a PIM-SM/SSM
 daemon; but as of now, I haven't seen any manual on how to make that work.=
 The configuration manual at&nbsp;<a href=3D"https://github.com/troglobit/p=
imd/blob/master/pimd.conf" class=3D"OWAAutoLink" id=3D"LPlnk257787">https:/=
/github.com/troglobit/pimd/blob/master/pimd.conf</a>&nbsp;has
 all the information about sparse-mode but nothing on SSM.&nbsp;</p>
<p>Does it support SSM?</p>
<p>If yes, then does it have any specific configuration options I should kn=
ow about?</p>
<p>Thanks,</p>
<p>Ali Rezaee</p>
<div id=3D"LPBorder_GT_14659801433950.9619462652056745" style=3D"margin-bot=
tom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id=3D"LPContainer_14659801433900.7859519886420956" cellspacing=3D"0"=
 style=3D"width: 90%; position: relative; overflow: auto; padding-top: 20px=
; padding-bottom: 20px; margin-top: 20px; border-top-width: 1px; border-top=
-style: dotted; border-top-color: rgb(200, 200, 200); border-bottom-width: =
1px; border-bottom-style: dotted; border-bottom-color: rgb(200, 200, 200); =
background-color: rgb(255, 255, 255);">
<tbody>
<tr valign=3D"top" style=3D"border-spacing: 0px;">
<td id=3D"ImageCell_14659801433910.5100303882864825" colspan=3D"1" style=3D=
"width: 250px; position: relative; display: table-cell; padding-right: 20px=
;">
<div id=3D"LPImageContainer_14659801433920.15772347537983822" style=3D"heig=
ht: 250px; position: relative; margin: auto; display: table; width: 250px; =
background-color: rgb(255, 255, 255);">
<a id=3D"LPImageAnchor_14659801433920.35167082896891566" href=3D"https://gi=
thub.com/troglobit/pimd/blob/master/pimd.conf" target=3D"_blank" style=3D"d=
isplay: table-cell; text-align: center;"><img aria-label=3D"Preview image w=
ith link selected. Double-tap to open the link." width=3D"250" height=3D"25=
0" style=3D"display: inline-block; margin-left: auto; margin-right: auto; m=
ax-width: 250px; max-height: 250px; height: 250px; width: 250px; border-wid=
th: 0px; vertical-align: bottom;" src=3D"https://avatars0.githubusercontent=
.com/u/183517?v=3D3&amp;s=3D400"></a></div>
</td>
<td id=3D"TextCell_14659801433920.34101906718899677" colspan=3D"2" style=3D=
"vertical-align: top; position: relative; padding: 0px; display: table-cell=
;">
<div id=3D"LPRemovePreviewContainer_14659801433920.2802111396489799"></div>
<div id=3D"LPTitle_14659801433930.38907366712048286" style=3D"top: 0px; col=
or: rgb(0, 120, 215); font-weight: normal; font-size: 21px; font-family: wf=
_segoe-ui_light, &quot;Segoe UI Light&quot;, &quot;Segoe WP Light&quot;, &q=
uot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sans-serif; line-h=
eight: 21px;">
<a id=3D"LPUrlAnchor_14659801433940.11219644491023484" href=3D"https://gith=
ub.com/troglobit/pimd/blob/master/pimd.conf" target=3D"_blank" style=3D"tex=
t-decoration: none;">troglobit/pimd</a></div>
<div id=3D"LPMetadata_14659801433940.4594022911536888" style=3D"margin: 10p=
x 0px 16px; color: rgb(102, 102, 102); font-weight: normal; font-family: wf=
_segoe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial=
, sans-serif; font-size: 14px; line-height: 14px;">
github.com</div>
<div id=3D"LPDescription_14659801433940.5506986042028428" style=3D"display:=
 block; color: rgb(102, 102, 102); font-weight: normal; font-family: wf_seg=
oe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sa=
ns-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: =
hidden;">
pimd - The original PIM-SM multicast routing daemon.</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<div id=3D"LPBorder_GT_14659800727250.5140644607615874" style=3D"margin-bot=
tom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id=3D"LPContainer_14659800727160.7840057110971179" cellspacing=3D"0"=
 style=3D"width: 90%; position: relative; overflow: auto; padding-top: 20px=
; padding-bottom: 20px; margin-top: 20px; border-top-width: 1px; border-top=
-style: dotted; border-top-color: rgb(200, 200, 200); border-bottom-width: =
1px; border-bottom-style: dotted; border-bottom-color: rgb(200, 200, 200); =
background-color: rgb(255, 255, 255);">
<tbody>
<tr valign=3D"top" style=3D"border-spacing: 0px;">
<td id=3D"ImageCell_14659800727190.6374185527133933" colspan=3D"1" style=3D=
"width: 250px; position: relative; display: table-cell; padding-right: 20px=
;">
<div id=3D"LPImageContainer_14659800727200.603464932321286" style=3D"height=
: 149px; position: relative; margin: auto; display: table; width: 149px; ba=
ckground-color: rgb(255, 255, 255);">
<a id=3D"LPImageAnchor_14659800727200.27550356951433397" href=3D"http://tro=
globit.github.io/pimd.html" target=3D"_blank" style=3D"display: table-cell;=
 text-align: center;"><img aria-label=3D"Preview image with link selected. =
Double-tap to open the link." width=3D"149" height=3D"149" style=3D"display=
: inline-block; margin-left: auto; margin-right: auto; max-width: 250px; ma=
x-height: 250px; height: 149px; width: 149px; border-width: 0px; vertical-a=
lign: bottom;" src=3D"https://camo.githubusercontent.com/365986a132ccd6a44c=
23a9169022c0b5c890c387/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f67=
69746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302=
e706e67"></a></div>
</td>
<td id=3D"TextCell_14659800727220.9829241996177422" colspan=3D"2" style=3D"=
vertical-align: top; position: relative; padding: 0px; display: table-cell;=
">
<div id=3D"LPRemovePreviewContainer_14659800727220.6930285660637738"></div>
<div id=3D"LPTitle_14659800727220.7937315200240274" style=3D"top: 0px; colo=
r: rgb(0, 120, 215); font-weight: normal; font-size: 21px; font-family: wf_=
segoe-ui_light, &quot;Segoe UI Light&quot;, &quot;Segoe WP Light&quot;, &qu=
ot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sans-serif; line-he=
ight: 21px;">
<a id=3D"LPUrlAnchor_14659800727230.9608951344488017" href=3D"http://troglo=
bit.github.io/pimd.html" target=3D"_blank" style=3D"text-decoration: none;"=
>Pimd | the Original PIM-SM Daemon - Troglobit</a></div>
<div id=3D"LPMetadata_14659800727230.595432465012931" style=3D"margin: 10px=
 0px 16px; color: rgb(102, 102, 102); font-weight: normal; font-family: wf_=
segoe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial,=
 sans-serif; font-size: 14px; line-height: 14px;">
troglobit.github.io</div>
<div id=3D"LPDescription_14659800727240.8713799396984596" style=3D"display:=
 block; color: rgb(102, 102, 102); font-weight: normal; font-family: wf_seg=
oe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sa=
ns-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: =
hidden;">
Pimd | the Original PIM-SM Daemon Nov 15th, 2015 7:26 pm pimd is a lightwei=
ght standalone PIM-SM/SSM v2 multicast routing daemon. It is the original &=
#8230;</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
</div>
</body>
</html>

--_000_DM3PR19MB0667B3C06ABF6A12251E4EA9B7550DM3PR19MB0667namp_--


From nobody Thu Jun 23 08:35:04 2016
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7D1B12D1D5; Thu, 23 Jun 2016 08:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 mxhfWplMXXci; Thu, 23 Jun 2016 08:34:52 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADE6512D1D1; Thu, 23 Jun 2016 08:34:51 -0700 (PDT)
X-AuditID: c618062d-f79886d000002334-dd-576bf79baac2
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 80.7B.09012.B97FB675; Thu, 23 Jun 2016 16:52:12 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0294.000; Thu, 23 Jun 2016 11:34:20 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "pim@ietf.org" <pim@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "isis-wg@ietf.org list (isis-wg@ietf.org)" <isis-wg@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: Computed multicast for SPRING
Thread-Index: AdHNYvY29SUhPXzFRJC1ciwPb7brLA==
Date: Thu, 23 Jun 2016 15:34:20 +0000
Message-ID: <E6C17D2345AC7A45B7D054D407AA205C4BD26118@eusaamb105.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/alternative; boundary="_000_E6C17D2345AC7A45B7D054D407AA205C4BD26118eusaamb105erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMLMWRmVeSWpSXmKPExsUyuXRPgu6c79nhBp9+slscPfSe1aLl3j12 iy8PbzJbHL/wm9GBxWPJkp9MAYxRXDYpqTmZZalF+nYJXBnXJnxhLtijVHF0ext7A+NZuS5G Tg4JAROJd9/uM0PYYhIX7q1n62Lk4hASOMoosfnMBjaQhJDAckaJvt0OIDabgIHEnv9fGEFs EYFVjBJ/ev1AbGEBNYnWs7NYuxg5gOLaEscO1EOU6ElsavsNNp9FQFXi9rInYDavgK/Ejac9 LCA2I9De76fWMIHYzALiEreezGeCuEdAYsme81C3iUq8fPyPFcJWkvj4ez47RH2+xJNti6Bm CkqcnPmEZQKj0Cwko2YhKZuFpAwiriOxYPcnNghbW2LZwtfMMPaZA4+ZkMUXMLKvYuQoLS7I yU03MtjECIyKYxJsujsY70/3PMQowMGoxMOrcCkrXIg1say4MvcQowQHs5II744/2eFCvCmJ lVWpRfnxRaU5qcWHGKU5WJTEecUeKYYLCaQnlqRmp6YWpBbBZJk4OKUaGBN1hC9IO0/r0Dq5 1FXdr2mirtXSZ2Eexx5OfcOz+aZ3tbPwFuWkW+WvPqYG8L75m7Ys/odABWd9p8KsZfc2PF64 c+6jC+kp721XFcwVtrN+MPXSixKtZv1Ds/daFnz9ftK0t3TlO6k3hbubrz7b3CDze/fH5cJ9 9yundcbtzT6wud5KQo7l3mYlluKMREMt5qLiRADHD7KEhgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/F0Vyiww9zZsggyi20t9Y6QTUnrk>
Subject: [pim] Computed multicast for SPRING
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2016 15:34:54 -0000

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

Hi PIM, SPRING, OSPF, ISIS

FYI, We've posted an update to the framework draft, as well as OSPF and ISI=
S drafts. This documents the approach and changes required to implement mul=
ticast as a hybrid of unicast tunnels and replication points in a SPRING-MP=
LS network. In this approach the multicast trees and the resulting FIB  are=
 derived entirely from information in the IGP.

At this point, this constitutes a complete proposal that can be critiqued i=
n its entirety. We'd welcome folks to read it though and welcome comments a=
nd questions...

The drafts of interest are:
https://datatracker.ietf.org/doc/draft-allan-spring-mpls-multicast-framewor=
k/
https://datatracker.ietf.org/doc/draft-allan-isis-spring-multicast/
https://datatracker.ietf.org/doc/draft-allan-ospf-spring-multicast/

Cheers!

--_000_E6C17D2345AC7A45B7D054D407AA205C4BD26118eusaamb105erics_
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">Hi PIM, SPRING, OSPF, ISIS<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">FYI, We&#8217;ve posted an update to the framework d=
raft, as well as OSPF and ISIS drafts. This documents the approach and chan=
ges required to implement multicast as a hybrid of unicast tunnels and repl=
ication points in a SPRING-MPLS network.
 In this approach the multicast trees and the resulting FIB &nbsp;are deriv=
ed entirely from information in the IGP.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">At this point, this constitutes a complete proposal =
that can be critiqued in its entirety. We&#8217;d welcome folks to read it =
though and welcome comments and questions&#8230;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The drafts of interest are:<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/doc/draft-al=
lan-spring-mpls-multicast-framework/">https://datatracker.ietf.org/doc/draf=
t-allan-spring-mpls-multicast-framework/</a>
<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/doc/draft-al=
lan-isis-spring-multicast/">https://datatracker.ietf.org/doc/draft-allan-is=
is-spring-multicast/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/doc/draft-al=
lan-ospf-spring-multicast/">https://datatracker.ietf.org/doc/draft-allan-os=
pf-spring-multicast/</a>
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Cheers!<o:p></o:p></p>
</div>
</body>
</html>

--_000_E6C17D2345AC7A45B7D054D407AA205C4BD26118eusaamb105erics_--


From nobody Fri Jun 24 09:07:07 2016
Return-Path: <agenda@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B00F312DC62; Fri, 24 Jun 2016 09:00:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <stig@venaas.com>, <pim-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160624160055.10933.49489.idtracker@ietfa.amsl.com>
Date: Fri, 24 Jun 2016 09:00:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/PXqA56YYHF_NQHJadecESG1RYRk>
Cc: pim@ietf.org
Subject: [pim] pim - Requested session has been scheduled for IETF 96
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2016 16:00:56 -0000

Dear Stig Venaas,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

pim Session 1 (2:30:00)
    Monday, Morning Session I 1000-1230
    Room Name: Charlottenburg I size: 80
    ---------------------------------------------
    

Special Note: Combined with MBONED


Request Information:


---------------------------------------------------------
Working Group Name: Protocols for IP Multicast
Area Name: Routing Area
Session Requester: Stig Venaas

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 50
Conflicts to Avoid: 
 First Priority: bier homenet i2rs mboned nvo3 rtgarea sdnrg
 Second Priority: bess rtgwg lisp



Special Requests:
  We would be happy to share our meeting slot with mboned.
---------------------------------------------------------

