| IETF 75 – Stockholm – Jul ‘09 | |
| L. Ong (Ciena) | |
| lyong@ciena.com | |
| OIF is incorporating ASON routing extensions defined by CCAMP (draft-ietf-ccamp-ason-routing-ospf) | ||||
| Additional Routing functionality requested: | ||||
| Layer-scoped Link Attributes | ||||
| Layer = VC-3, VC-4 | ||||
| Connections available at a particular layer (alluded in ASON draft) | ||||
| Attributes (e.g., metric) that differ for a layer | ||||
| Local Connection Type | ||||
| CP or TCP (switch or terminate) | ||||
| Within layer, not multilayer/adaptation-related | ||||
| Looking for better solution than ISCD/IACD | ||||
| NSAP format Local Node Prefix | ||||
| In addition to IPv4 and IPv6 formats | ||||
| CCAMP action requested | ||||
| Look for future draft input by interested parties | ||||
draft on ASON routing extensions
| Draft-ietf-ccamp-ason-routing-ospf-08.txt | |||
| Routing information scope | |||
| Link advertisement supplements – local/remote TE Router ID | |||
| Link attributes | |||
| Local adaptation | |||
| Bandwidth accounting | |||
| Technology specific extensions out of scope | |||
| Reachability extensions | |||
| Node Local Prefix | |||
| Router ID advertising on behalf of multiple TE Router IDs | |
| Link Attributes | ||
| Bandwidth | ||
| Metric | ||
| Admin group | ||
| Diversity (SRLG) | ||
| Adaptation | ||
| Local connection type | ||
| Issues | ||
| No way to advertise layer-scoped link attributes | ||
| Issues with advertising local connection type | ||
| ITU-T layers in an SDH link can include | ||
| VT11 | ||
| VT12 | ||
| VC2 | ||
| VC3/STS1 | ||
| VC4/STS3c | ||
| VC4-4c/STS-12c | ||
| VC4-16c/STS-48c | ||
| VC4-64c/STS-192 | ||
| Attributes could be identical for all layers supported by the link | ||
| Could be different for a specific layer | ||
ISCD for SDH with layer-scoped BW
| As tested – expands with technology-specific bandwidth per ITU-T layer, using RFC 3946 signal types |
| Distinguish between CP (connection point) and TCP (termination connection point) | |
| CP will allow connections to cross, TCP will not | |
| Previous discussion has linked TCP with adaptation and use of multiple ISCDs or IACD | |
| In our case we just want to know if transit is possible | |
| ASON routing extension draft allows advertisement of reachability as in draft-ietf-ospf-te-node-id-06.txt | |
| Adds Node IPv4 local prefix and Node IPv6 local prefix sub-TLVs to allow advertisement of blocks | |
| Similar capability supported in OIF testing in exp. Sub-TLV. | |
| Desire from some OIF members to have NSAP format address included as an option | |
| RFC 1888 originally contained procedure for putting a truncated NSAP address into an IPv6 address format | |
| This was removed when RFC 1888 was replaced by RFC 4548, which only defines mapping from IPv4 and IPv6 addresses to the NSAP format |