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