40 likes | 56 Views
This document discusses the general requirements and IP telephony requirements for ETS. It focuses on protocols that can be applied within a single administrative domain and includes perspectives from "home" and "foreign" networks. Common practice of over provisioning is also discussed.
E N D
IETF-San DiegoIEPREP WG, Aug 2004Status Ken Carlberg
Past Stuff • Done • RFC-3689: General Requirements for ETS, 2/04 • RFC-3690: IP Telephony Requirements for ETS, 2/04 • IESG pipeline • draft-ietf-ieprep-framework-09.txt • Framework for Supporting ETS in IP Telephony • awaiting feedback
Current Efforts • draft-ietf-ieprep-domain-req-01.txt • ETS Requirements for Single Administrative Domain • Extension of General Requirements (rfc-3689) • Not focused on a particular application nor set of users – ie, effort is rather general • draft-ietf-ieprep-domain-frame-01.txt • Focusing on protocols that can be applied within a domain • Common Practice: Over Provisioning • time honored tradition • Includes perspective of “home” and “foreign” networks • Stems from discussion at San Francisco IETF, and subsequent thread on IEPREP list
Summary • Single Domain drafts have not changed much since initial submission • -01 versions are simply a clean up of -00 • Early feedback on list, but nothing from -01 • Last Call? • Wrap it up and move on