Re: [Gen-art] Review: draft-ietf-pim-join-attributes-for-lisp-05

Lucy yong <> Thu, 01 December 2016 19:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4149B129EC5 for <>; Thu, 1 Dec 2016 11:40:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.117
X-Spam-Status: No, score=-7.117 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=-2.896, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0f8Q8Ub9VjUW for <>; Thu, 1 Dec 2016 11:40:44 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 38964129D74 for <>; Thu, 1 Dec 2016 11:32:00 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DBT37455; Thu, 01 Dec 2016 19:31:57 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 1 Dec 2016 19:31:56 +0000
Received: from ([]) by ([]) with mapi id 14.03.0301.000; Thu, 1 Dec 2016 11:31:52 -0800
From: Lucy yong <>
To: Dino Farinacci <>, Jari Arkko <>
Thread-Topic: [Gen-art] Review: draft-ietf-pim-join-attributes-for-lisp-05
Thread-Index: AQHSS9dg0znVJP8wr0OgiACQmQwULKDz+ouA//99iYA=
Date: Thu, 01 Dec 2016 19:31:51 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57B93C5E@dfweml501-mbb>
References: <2691CE0099834E4A9C5044EEC662BB9D572E1B66@dfweml501-mbb> <> <2691CE0099834E4A9C5044EEC662BB9D572E282A@dfweml501-mbb> <> <2691CE0099834E4A9C5044EEC662BB9D572E28BC@dfweml501-mbb> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.58407AAD.02E1, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 65eb77b6b866a05d876ca3563b585257
Archived-At: <>
Cc: "" <>, General Area Review Team <>, Stig Venaas <>
Subject: Re: [Gen-art] Review: draft-ietf-pim-join-attributes-for-lisp-05
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 01 Dec 2016 19:40:46 -0000

Hi Dino,

Sorry, I did not have time to study RFC6831 for this review work and may not interpret the draft properly by reading it. I trust you on the protocol design and have no objection on Jari's decision.

Could you make this sentence more readable?

   It determines the downstream destination for unicast head-end replication and identifies the
   receiver ETR that needs to be notified should the root of the
   distribution tree move to another site.

"should be", "moving"?

-----Original Message-----
From: Dino Farinacci [] 
Sent: Thursday, December 01, 2016 1:07 PM
To: Jari Arkko
Cc: Lucy yong;; General Area Review Team; Stig Venaas
Subject: Re: [Gen-art] Review: draft-ietf-pim-join-attributes-for-lisp-05

> Lucy,
> Many thanks for your review.
> Dino, Stig, does this discussion lead you to consider adding some clarifications to the document? I am not going to require those (just posted a no-obj for the document on today’s telechat), but wanted to give you an opportunity to consider that.
> Jari

The base LISP multicast architecture is all explained in RFC6831. From the type of commentary from Lucy’s email, it led me to believe she (1) had not read RFC6831 or (2) did not understand the content of RFC6831.

Discussing how LISP multicast works in a PIM document is a misplacement of information and risks contradicting what is in the LISP published RFCs.