Hi Jouni,
Thanks very much for the comments. I fixed the nits in the draft.
Regarding the Switching Capability-specific information field, we had the
discussion in WG, and here's the summary/conclusion:
It's decided that this document will just define the availability TLV, and a
new draft
Hi Jouni,
You're right that the current draft text doesn't provide any information about
the discussion.
So how about add the following text at the end of section 3.1:
This document only defines the Availability TLV, how the existing Switching
Capability makes use of the Availability TLV
Hi,
> On Oct 17, 2016, at 1:06 AM, Yemin (Amy) wrote:
>
> Hi Jouni,
>
> Thanks very much for the comments. I fixed the nits in the draft.
>
> Regarding the Switching Capability-specific information field, we had the
> discussion in WG, and here's the
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
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
Send again.
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-ART reviewer for this draft.
> 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