|
| 1 | +--- https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12689&rfc_flag=0 |
| 2 | ++++ /idtracker/draft-ietf-isis-link-attr/ |
| 3 | +@@ -69,2 +69,4 @@ |
| 4 | +-This draft is basically ready for publication, but has nits and more |
| 5 | +-... |
| 6 | ++This draft is basically ready for publication, but has nits that |
| 7 | ++should be fixed before publication. |
| 8 | ++ |
| 9 | ++This is a short ... |
| 10 | +@@ -84,1 +86,1 @@ |
| 11 | +-Traffic Engineering (TE)", > RFC 3784, June 2004. and more ... |
| 12 | ++Traffic Engineering (TE)", > RFC 3784, June ... |
| 13 | +@@ -91,4 +93,1 @@ |
| 14 | +-to be clear. What does an implementation do if a link is part of some |
| 15 | +-local protection? No reference is given to the process of computing a |
| 16 | +-protection path so it is not well defined what an excluded link should |
| 17 | +-not be included in. |
| 18 | ++to be clear. What does an implementation do if a link ... |
| 19 | +@@ -103,1 +102,3 @@ |
| 20 | +-length of 2 octets. and more ... |
| 21 | ++length of 2 octets. |
| 22 | ++ |
| 23 | ++I think that ... |
| 24 | +@@ -109,1 +110,3 @@ |
| 25 | +-length of 2 octets. and more ... |
| 26 | ++length of 2 octets. |
| 27 | ++ |
| 28 | ++I think that ... |
| 29 | +@@ -128,5 +131,2 @@ |
| 30 | +-2007-03-14 03 |
| 31 | +-[fenner] I thought I had put this on the 3/8 telechat, but I screwed |
| 32 | +-up. I'll put it on the telechat after the IETF. I won't be AD any |
| 33 | +-more, but hopefully the document will get approved. |
| 34 | +-The downrefs have been mentioned in the Last Call. |
| 35 | ++2007-03-14 03 [fenner] I thought I had put this on the 3/8 telechat, |
| 36 | ++but I screwed up. I'll put it on the telechat after the IETF ... |
| 37 | +@@ -140,1 +140,3 @@ |
| 38 | +-actions that need to be completed. and more ... |
| 39 | ++actions that need to be completed. |
| 40 | ++ |
| 41 | ++First, in the IS-IS ... |
| 42 | +@@ -145,1 +147,3 @@ |
| 43 | +-actions that need to be completed. and more ... |
| 44 | ++actions that need to be completed. |
| 45 | ++ |
| 46 | ++First, in the IS-IS ... |
| 47 | +@@ -168,1 +172,1 @@ |
| 48 | +-needed but it might be a bit long. |
| 49 | ++needed but it might be a ... |
| 50 | +@@ -181,1 +185,3 @@ |
| 51 | +-and more ... |
| 52 | ++Hi, |
| 53 | ++ |
| 54 | ++I'm following up on Alex's AD Review ... |
| 55 | +@@ -198,1 +204,3 @@ |
| 56 | +-> Definition of an IS-IS Link Attribute sub-TLV > and more ... |
| 57 | ++> Definition of an IS-IS Link Attribute sub-TLV > > draft-ietf-isis- |
| 58 | ++link-attr-01.txt > > Abstract > > This document defines a sub-TLV |
| 59 | ++called "Link-attributes" carried > within the ... |
0 commit comments