Updated diff (should have committed with _idtracker_12689_)
- Legacy-Id: 512
This commit is contained in:
parent
7cdffc0fa2
commit
4c6b9882d0
|
@ -1,32 +1,29 @@
|
|||
--- https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12689&rfc_flag=0
|
||||
+++ /idtracker/draft-ietf-isis-link-attr/
|
||||
@@ -69,2 +69,4 @@
|
||||
@@ -40,2 +40,3 @@
|
||||
-This draft is basically ready for publication, but has nits and more
|
||||
-...
|
||||
+This draft is basically ready for publication, but has nits that
|
||||
+should be fixed before publication.
|
||||
+
|
||||
+This is a short ...
|
||||
@@ -84,1 +86,1 @@
|
||||
-Traffic Engineering (TE)", > RFC 3784, June 2004. and more ...
|
||||
+Traffic Engineering (TE)", > RFC 3784, June ...
|
||||
@@ -91,4 +93,1 @@
|
||||
@@ -51,1 +52,1 @@
|
||||
-Traffic Engineering (TE)", > RFC3784, June 2004. and more ...
|
||||
+Traffic Engineering (TE)", > RFC3784, June ...
|
||||
@@ -56,4 +57,1 @@
|
||||
-to be clear. What does an implementation do if a link is part of some
|
||||
-local protection? No reference is given to the process of computing a
|
||||
-protection path so it is not well defined what an excluded link should
|
||||
-not be included in.
|
||||
+to be clear. What does an implementation do if a link ...
|
||||
@@ -103,1 +102,3 @@
|
||||
@@ -66,1 +64,2 @@
|
||||
-length of 2 octets. and more ...
|
||||
+length of 2 octets.
|
||||
+
|
||||
+I think that ...
|
||||
@@ -109,1 +110,3 @@
|
||||
@@ -71,1 +70,2 @@
|
||||
-length of 2 octets. and more ...
|
||||
+length of 2 octets.
|
||||
+
|
||||
+I think that ...
|
||||
@@ -128,5 +131,2 @@
|
||||
@@ -83,5 +83,2 @@
|
||||
-2007-03-14 03
|
||||
-[fenner] I thought I had put this on the 3/8 telechat, but I screwed
|
||||
-up. I'll put it on the telechat after the IETF. I won't be AD any
|
||||
|
@ -34,25 +31,22 @@
|
|||
-The downrefs have been mentioned in the Last Call.
|
||||
+2007-03-14 03 [fenner] I thought I had put this on the 3/8 telechat,
|
||||
+but I screwed up. I'll put it on the telechat after the IETF ...
|
||||
@@ -140,1 +140,3 @@
|
||||
@@ -93,1 +90,2 @@
|
||||
-actions that need to be completed. and more ...
|
||||
+actions that need to be completed.
|
||||
+
|
||||
+First, in the IS-IS ...
|
||||
@@ -145,1 +147,3 @@
|
||||
@@ -97,1 +95,2 @@
|
||||
-actions that need to be completed. and more ...
|
||||
+actions that need to be completed.
|
||||
+
|
||||
+First, in the IS-IS ...
|
||||
@@ -168,1 +172,1 @@
|
||||
@@ -112,1 +111,1 @@
|
||||
-needed but it might be a bit long.
|
||||
+needed but it might be a ...
|
||||
@@ -181,1 +185,3 @@
|
||||
@@ -121,1 +120,2 @@
|
||||
-and more ...
|
||||
+Hi,
|
||||
+
|
||||
+I'm following up on Alex's AD Review ...
|
||||
@@ -198,1 +204,3 @@
|
||||
@@ -133,1 +133,3 @@
|
||||
-> Definition of an IS-IS Link Attribute sub-TLV > and more ...
|
||||
+> Definition of an IS-IS Link Attribute sub-TLV > > draft-ietf-isis-
|
||||
+link-attr-01.txt > > Abstract > > This document defines a sub-TLV
|
||||
|
|
Loading…
Reference in a new issue