[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ason-routing-reqts: issue 1 addressing
As noted in the CCAMP minutes and the DT's presentation, the ASON routing DT had three issues regarding GMPLS support for which they lacked agreement and request support of the WG. The issues are identified in Section 7 (Conclusions) of the draft:
ftp://ftp.isi.edu/internet-drafts/draft-ietf-ccamp-gmpls-ason-routing-reqts-02.txt
I will post three separate email threads to cover each issue. The first issue is on address reachability. The following is the text from the draft:
Some members of the Design Team noted that reachability information (as described in Section 4.5.3) may be advertised as a set of UNI Transport Resource address prefixes (assigned and selected consistently in their applicability scope). These members of the Design Team raised a concern that existing methods of advertising reachability may need to be examined (on a per-protocol basis) to determine if they are also applicable for UNI Transport Resource addresses. They invite CCAMP discussion on this aspect.
Deborah