[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Questions regarding draft-ietf-ccamp-gmpls-mln-reqs-01
- To: firstname.lastname@example.org
- Subject: Questions regarding draft-ietf-ccamp-gmpls-mln-reqs-01
- From: Jeroen van der Ham <email@example.com>
- Date: Wed, 19 Jul 2006 17:12:27 +0200
- User-agent: Thunderbird 184.108.40.206 (Macintosh/20060530)
I am trying to understand the text in
draft-ietf-ccamp-gmpls-mln-reqs-01, but some things are not completely
clear to me, I hope someone can explain them:
- I believe that the draft often uses the term ISCD often where ISC is
meant. If I understand it correctly, different ISCDs can be announced
for a given interface at different times, for example because the
available bandwidth is changing.
- At the end of the first paragraph in Section 3.3 it states:
[...] in carrier's networks that are based on multiple layers,
switching technologies, or ISCDs.
I think that this statement should not mention ISCDs at all, because it
makes no sense in that context. Especially if you also read the
following statement at the end of the third paragraph in section 4.3:
The ISCD does not "identify" network layers, it uniquely characterizes
information associated to one or more network layers.
- I find the example in section 4.2.1 to be very briefly explained, it
could do with a better explanation of what is going on.
One improvement would be to state explicitly which three(!) ways are
possible for setting up an PSC LSP across this device:
1) Terminating on interface #b
2) Terminating on interface #a
3) Going through the device towards a neighboring PSC node.
It would also help to explain that the existance of possibility 1 is the
sole reason that the device is a hybrid device. And that possibility 1
is also the reason why the PSC is advertised on Link2.
Other minor corrections:
Section 1 mixes the notation of VC-x and VCx
Section 4.2.1 has swtching, where it should switching