• Revised I-D Needed - Issue raised by WG
  • Awaiting Expert Review/Resolution of Issues Raised
  • Awaiting External Review/Resolution of Issues Raised
  • Awaiting Merge with Other Document
  • Author or Editor Needed
  • Waiting for Referenced Document
  • Waiting for Referencing Document
  • Revised I-D Needed - Issue raised by WGLC
  • Revised I-D Needed - Issue raised by AD
  • Revised I-D Needed - Issue raised by IESG
  • Doc Shepherd Follow-up Underway
  • Other - see Comment Log

IETF :: lisp

Current state: WG Document

Viewing the last 20 entries. Show full log.

(System)

RFC published

(System)

post-migration administrative database adjustment to the No Objection position for Stewart Bryant

(System)

post-migration administrative database adjustment to the No Objection position for Ralph Droms

(System)

post-migration administrative database adjustment to the No Objection position for Stephen Farrell

(System)

post-migration administrative database adjustment to the No Objection position for Adrian Farrel

(System)

post-migration administrative database adjustment to the No Objection position for Ronald Bonica

(System)

IANA Action state changed to No IC

Cindy Morgan

State changed to RFC Ed Queue from Approved-announcement sent.

Amy Vezza

IESG has approved and state has been changed to Approved-announcement sent

Amy Vezza

Closed "Approve" ballot

Amy Vezza

Approval announcement text regenerated

Amy Vezza

Ballot writeup text changed

Jari Arkko

State changed to Approved-announcement to be sent from IESG Evaluation::AD Followup.

Adrian Farrel

[Ballot Position Update] Position for Adrian Farrel has been changed to No Objection from Discuss

(System)

Added new revision

Adrian Farrel

[Ballot comment]
The title talks about "LISP for multicast environments" but the Abstract
is specific to "inter-domain multicast routing". Should the document
title be updated accordingly or is the Abstract wrong?

It is possible that the confusion is at bullet 2 of Section 2 where it
is implied that a "domain" is a LISP site such that "inter-domain" means
between LISP sites. It would be helpful not to re-use "domain" in ths
way (we are used to it meaning inter-AS and inter-area).

Since multicast between LISP sites is just a special case of multicast
using LISP, you could stike the text from the Abstract.

Adrian Farrel

[Ballot discuss]
Updating my Discuss in line with revision -13

As previously noted on other LISP documents, I would like a pointer to the generic caveat text being added to the main LISP spec. Did I miss it in this revision? I can't find it.

Suitable text can be found in draft-ietf-lisp-map-versioning

Stewart Bryant

[Ballot comment]
The following issue would be a blocking comment in an architecture or a standards track specification, but I am persuaded that in the specification of an experimental protocol subject to the limitation described in draft-ietf-lisp-21 the resolution of these comments should be left to the authors.

This document defines a set of terms EID, RLOC etc which at first sight seem identical to the unicast terms. However the description of their operation seems to make them different objects, in which case they need different names. If the names are to be common, there needs to be a separation of the name from the mode of operation.

Where the object is identical to the unicast term (LISP Header?) the object should not need to be redefined in this document since this invites issues of subtle difference between the competing definitions.

======

"By using the traffic engineering features of LISP" needs a ref.

The subtleties of different m/c paths surely belongs after the basic description rather than as the first item

The protocols in section 7 need references

Mpriority seems to lack a definition

Stewart Bryant

[Ballot Position Update] Position for Stewart Bryant has been changed to No Objection from Discuss

(System)

Sub state has been changed to AD Follow up from New Id Needed

Viewing the last 20 entries. Show full log.