The Routing Over Large Clouds Mailing List Archive by date[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Last Call for draft-ietf-rolc-apr-00.txt
Dilip, > > The implication is that QoS requirements would be considered as a > > guide to setup SVCs. Yes, there is also a belief that an SVC would > > provide better QoS (e.g. delay) since it avoids IP level handling > > costs at intermediate nodes. > > I don't think we should be making assumptions like that in an architectural > document: that is an implementation issue. I certainly know of some ATM switches > with higher latency (under some traffic conditions) than routers .... :-) > > We can, however, make the assertion that the QoS characteristics of > the ATM SVC would be based on the QoS requirements of the higher > layers. Yes. Assuming a direct SVC were deemed to be the right mechanism to use for that particular QoS at the time of the query. > The belief that ATM SVCs are more desirable than multiple IP > hops is one that is in line with the objectives of ROLC. I disagree: I thought the objective of ROLC was to provide a protocol mechanism which would *allow* for shortcut VCCs. There is nothing in the ROLC charter (and there is certainly nothing in the NHRP draft) about whether that is always the desirable outcome or not. The charter needs updating if you think that this assumption is an implicit part of ROLC's work. I repeat, this draft is an architectural draft with much wider implications than the narrow focus of ROLC. That was the gist of my previous posting asking that this draft be posted much more widely than just the ROLC group. There is an implicit assumption being made that this draft represents the views of the IAB (same as 1620), not just the ROLC group. If its consumption is limited to just the ROLC focus then it becomes a much less useful and less relevant piece of work. I assume that Andy will be producing an updated list of goals/milestones in the charter to match the APR work: I apologise for having missed the discussions on the justification of why this work is in the ROLC group which must have occurred in Stockholm. > -- Dilip. > Andrew ******************************************************************************** Andrew Smith TEL: +1 408 764 1574 Technology Synergy Unit FAX: +1 408 988 5525 Bay Networks, Inc. E-m: asmith@baynetworks.com Santa Clara, CA ********************************************************************************
|
|