On 01 Dec 2016, at 22:01, Dino Farinacci wrote:
> There is no other text in the email. So can’t be sure what you are saying.
> I’m guessing you are fine with the proposed text?
yes, the one that you proposed
signature.asc
Description: Message signed with OpenPGP using
Subject: Re: [Gen-art] Review: draft-ietf-pim-join-attributes-for-lisp-05
> OK, forget my suggestion. I have a difficulty to parse this sentence
> (second part)
>
> It determines the downstream destination for unicast head-end
> replication and identifies the receiver
There is no other text in the email. So can’t be sure what you are saying. I’m
guessing you are fine with the proposed text?
My co-authors have to agree though. ;-)
Dino
> On Dec 1, 2016, at 11:55 AM, Jari Arkko wrote:
>
> That would work for me.
>
> Jari
>
That would work for me.
Jari
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
From: Dino Farinacci [mailto:farina...@gmail.com]
> Sent: Thursday, December 01, 2016 1:45 PM
> To: Lucy yong
> Cc: Jari Arkko; draft-ietf-pim-join-attributes-for-l...@tools.ietf.org;
> General Area Review Team; Stig Venaas
> Subject: Re: [Gen-art] Review: draft-ietf-pim-join-attributes-for
-Original Message-
From: Dino Farinacci [mailto:farina...@gmail.com]
Sent: Thursday, December 01, 2016 1:45 PM
To: Lucy yong
Cc: Jari Arkko; draft-ietf-pim-join-attributes-for-l...@tools.ietf.org; General
Area Review Team; Stig Venaas
Subject: Re: [Gen-art] Review: draft-ietf-pim-join
> 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”?
I do not
com]
Sent: Thursday, December 01, 2016 1:07 PM
To: Jari Arkko
Cc: Lucy yong; draft-ietf-pim-join-attributes-for-l...@tools.ietf.org; 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.
>
&g
> 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
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
> Two. One at all LISP sites (not one per LISP site) and part of the overlay
> and possibly one in the underlay.
> [Lucy] Thank, Dino. This is helpful. So the attributes proposed in this draft
> is used in the first PIM instance, right? These attributes are only used by
> ETRs to send
Dino,
please see inline below.
>> the draft assumes that PIM works within individual LISP sites but PIM
>> mcast transport may not be supported among LISP sites. However the
>> mechanism itself does not enforce a unique (unicast or mcast)
>> underlay transport among LISP sites. Could some
>> the draft assumes that PIM works within individual LISP sites but PIM
>> mcast transport may not be supported among LISP sites. However the
>> mechanism itself does not enforce a unique (unicast or mcast) underlay
>> transport among LISP sites. Could some ETRs request unicast transport,
>>
:59 PM
> *To:* A. Jean Mahoney; General Area Review Team;
> 'draft-ietf-pim-join-attributes-for-lisp....@tool.ietf.org'
> *Subject:* [Gen-art] Review:
> draft-ietf-pim-join-attributes-for-lisp-05
>
>
>
> I am the assigned Gen-ART reviewer for this draft. The General Ar
-for-lisp@tool.ietf.org'
*Subject:* [Gen-art] Review: draft-ietf-pim-join-attributes-for-lisp-05
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed by the
IESG for the IETF Chair. Please treat these comments just like
> the draft assumes that PIM works within individual LISP sites but PIM mcast
> transport may not be supported among LISP sites. However the mechanism itself
> does not enforce a unique (unicast or mcast) underlay transport among LISP
> sites. Could some ETRs request unicast transport, other
Send again. fix some template info.
From: Lucy yong
Sent: Monday, October 17, 2016 1:59 PM
To: A. Jean Mahoney; General Area Review Team;
'draft-ietf-pim-join-attributes-for-lisp@tool.ietf.org'
Subject: [Gen-art] Review: draft-ietf-pim-join-attributes-for-lisp-05
I am the assigned Gen
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team
(Gen-ART) reviews all IETF documents being processed by the IESG for the IETF
Chair. Please treat these comments just like any other last call comments.
For more information, please see the FAQ at
18 matches
Mail list logo