Mdnsext requirements draft-lynn-mdnsext-requirements Kerry Lynn Stuart Cheshire 06 November 2012.
-
Upload
emmeline-hensley -
Category
Documents
-
view
213 -
download
0
Transcript of Mdnsext requirements draft-lynn-mdnsext-requirements Kerry Lynn Stuart Cheshire 06 November 2012.
![Page 1: Mdnsext requirements draft-lynn-mdnsext-requirements Kerry Lynn Stuart Cheshire 06 November 2012.](https://reader036.fdocuments.net/reader036/viewer/2022082820/5697bf731a28abf838c7f59a/html5/thumbnails/1.jpg)
mdnsext requirementsdraft-lynn-mdnsext-
requirements
Kerry Lynn <[email protected]>Stuart Cheshire <[email protected]>06 November 2012
![Page 2: Mdnsext requirements draft-lynn-mdnsext-requirements Kerry Lynn Stuart Cheshire 06 November 2012.](https://reader036.fdocuments.net/reader036/viewer/2022082820/5697bf731a28abf838c7f59a/html5/thumbnails/2.jpg)
mdnsext requirements
Scalable
Usable
Deployable
![Page 3: Mdnsext requirements draft-lynn-mdnsext-requirements Kerry Lynn Stuart Cheshire 06 November 2012.](https://reader036.fdocuments.net/reader036/viewer/2022082820/5697bf731a28abf838c7f59a/html5/thumbnails/3.jpg)
Scalable
• Enable DNS-based Service Discovery across lots of links (LoL)
• Suitable for both local (zero-config) and global (little-config) use
• Scalablility in terms of:– Network traffic– CPU and memory requirements on network entities
• Architecture– Common terminology/concepts (e.g. many subnets may
“map” to a link, many links may “map” to a subnet)– Granularity of services available on a server (extend
the traditional notion of service?)
![Page 4: Mdnsext requirements draft-lynn-mdnsext-requirements Kerry Lynn Stuart Cheshire 06 November 2012.](https://reader036.fdocuments.net/reader036/viewer/2022082820/5697bf731a28abf838c7f59a/html5/thumbnails/4.jpg)
Usable
• Zero configuration operation possible but not mandatory. Zero-config is supported by the protocols, but administrative control is also available on networks or in situations where that is desirable (e.g. user opts-in for service to be publicly visible)
• A smooth continuum of operation and experience from local link to site to global, rather than wildly different incompatible modes of operation at different network scales
• User interface (huge flat list is not user friendly)
![Page 5: Mdnsext requirements draft-lynn-mdnsext-requirements Kerry Lynn Stuart Cheshire 06 November 2012.](https://reader036.fdocuments.net/reader036/viewer/2022082820/5697bf731a28abf838c7f59a/html5/thumbnails/5.jpg)
Deployable
• Incremental deployability (e.g. "islands" of infrastructure-less functionality can be merged)
• Identify what changes to existing network elements will be required, and attempt to minimize those changes (e.g. may be easier to revise the clients)
• Suitable out-of-the box defaults should enable zero-config use on many small- to medium-sized networks, while still allowing for administrative control in networks where that's appropriate
![Page 6: Mdnsext requirements draft-lynn-mdnsext-requirements Kerry Lynn Stuart Cheshire 06 November 2012.](https://reader036.fdocuments.net/reader036/viewer/2022082820/5697bf731a28abf838c7f59a/html5/thumbnails/6.jpg)
Secure
• Authorization versus authentication (e.g. which services are authorized to advertise?)
• Avoid manual config of every service entry in a directory