Re: [Seamoby] RE: [NSIS] Re: draft-westphal-nsis-qos-mobileip-00. txt

> CT is not a service establishment protocol; it tranports
       forwarding context, not service description parameters. Some
       of the forwarding context *may* be the original service description
       parameters, but many *may* be derived values that allow a more
       representative description of the AR forwarding context.

If the service description parameters are involved in fowarding, then the two are the same, right? Will there be any
difference for QoS?

> For the two groups should discuss the common parameters would be a
       violation of the respective charters. I think that this is an
excellent
       idea, but I believe it will have to take place outside of the
NSIS/Seamoby
       wgs, and I suggest that it would be best if we knew what the CT/NSIS
       protocols were - at the very least, we can proceed with the
definition
       of the protocols.

We have to make sure the two protocols work well together.

CT is not specific to QoS, so I don't see any overlap, but when it comes time to define the QoS feature context type, perhaps
that definition can be done by the NSIS group, or in conjunction with it in some way. Requirements, for example.

            jak

_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby