Yakov - WG/ Document Status Update
        - See Slides. (To be uploaded to IETF web site?)

draft-ietf-idr-rfc258bis-10.txt (Multiprotocol Extensions)

Graceful Restart Mechanisms
        - Implemented, interoperable, need to make edits to satisfy IESG
requirements
        - Loa? - This is holding up MPLS document.
        - Yakov - Yes, hopefully revision addresses IESG comments.

Submitted to IESG:
bgp-prefix-orf
idr-route-filter

No new progress
        - list of documents

===============================================================
QoS Support in BGP - Andreas Terzis
draft-liang-bgp-qos-00.txt

Authors made a few updates to presentation on the IETF web site.
Updated presentation to be posted to the IETF web sie after the meeting.   

Preliminary idea. Reason for presentation is to solicit comments &
questions.

Zandra pala (?). Is there one set of metrics for each AS? A: Propose a
standard set of metrics.

Larry Dennison: Set of metrics per AS-Path to tag different latencies and
bandwidths. A: QoS metrics need to be updated in the AS as the BGP update
message is propagated.

Tony Tauber: Update is touched multiple times in the AS? A: Performance
needs to be measured. Includes not only inter-domain links, but also the QoS
within the domain. QoS metrics can be dynamic (queuing delay) or static
(e.g., propagation delay). Initally, the plan is to support static metrics.
Would need to extend IGP to support multiple paths across the AS. This has
not been addressed yet. In order to force packet to traverse the advertised
path MPLS could be used.

Sabhi (?): What happens if path goes through route reflector? Normally, a RR
does not modify updates? A: Internal components of the QoS metric could be
updated by the RR bassed upon configuration. In this approach, the RR would
need to update the message. The RR would also need to generate multiple
paths.

Sabhi (?): What happens if there are multiple links to the upstream AS? A:
After DPSA, potentially multiple links would be advertised.

Yakov: In order to achieve routing system scalability, a tradeoff is made by
losing information. For example, in BGP to lose much of the IGP information
at the AS boundaries. These are not trivial questions, which have been
attempted to be addressed for the past 15 years. Before getting to specific
coding, the abstraction of information should first be considered.

Discussion on the mailing list is invited.