Last Call: draft-ietf-roll-terminology-13.txt (Terms used in Ruting for Low power And Lossy Networks) to Informational RFC
The IESG has received a request from the Routing Over Low power and Lossy networks WG (roll) to consider the following document: - 'Terms used in Ruting for Low power And Lossy Networks' draft-ietf-roll-terminology-13.txt as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2013-10-17. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The documents provides a glossary of terminology used in routing requirements and solutions for networks referred to as Low power and Lossy Networks (LLN). An LLN is typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links. There is a wide scope of application areas for LLNs, including industrial monitoring, building automation (e.g. Heating, Ventilating, Air Conditioning, lighting, access control, fire), connected home, healthcare, environmental monitoring, urban sensor networks, energy management, assets tracking, refrigeration. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-roll-terminology/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-roll-terminology/ballot/ No IPR declarations have been submitted directly on this I-D.
IETF 88 - Meeting Information
88th IETF Meeting Vancouver, BC, Canada November 3-8, 2013 Host: Huawei Meeting venue: Hyatt Regency Vancouver: http://vancouver.hyatt.com/en/hotel/home.html Register online at: http://www.ietf.org/meeting/88/ 1. Registration 2. Visas Letters of Invitation 3. Accommodations 4. Companion Program 5. Social Event - there will not be a social event at IETF 88 1. Registration A. Early-Bird Registration - USD 650.00 Pay by Friday, 25 October 2013 UTC 24:00 B. After Early-Bird cutoff - USD 800.00 C. Full-time Student Registrations - USD 150.00 (with proper ID) D. One Day Pass Registration - USD 350.00 E. Registration Cancellation Cut-off for registration cancellation is Monday, 28 October 2013 at UTC 24:00. Cancellations are subject to a 10% (ten percent) cancellation fee if requested by that date and time. F. Online Registration and Payment ends Friday, 1 November 2013, 1700 local Vancouver time. G. On-site Registration starting Sunday, 3 November 2013 at 1100 local Vancouver time. 2. Visas Letters of Invitation: Information on Visiting Canada, please visit: http://www.cic.gc.ca/english/visit/index.asp After you complete the registration process, you can request an electronic IETF letter of invitation as well. The registration system also allows for you to request a hard copy IETF letter of invitation. You may also request one at a later time by following the link provided in the confirmation email. Please note that the IETF Letter of Invitation may not be sufficient for obtaining a visa to enter Canada. 3. Accommodations The IETF is holding a block of guest rooms at the Hyatt Regency Vancouver, the meeting venue, as well as at the overflow hotel Fairmont Hotel Vancouver, which is located across the street from the Hyatt. Room Rates include in room high-speed Internet access. Taxes of 16.5% (hotel room tax, GST and Destination Management Fee) are excluded from the guestroom rate and are subject to change. Room rates DO NOT include daily breakfast. Reservations Cut off Date: Hyatt Regency Vancouver - 20 October 2013 Fairmont Hotel Vancouver - 11 October 2013 For additional information on rates and policies, please visit: http://www.ietf.org/meeting/88/hotel.html 4. Companion Program If you are traveling with a friend or family member over 18 years of age you can register them for the IETF Companion Program for only USD 25.00 Benefits include: - A special welcome reception for companions from 1630-1730 on Sunday, 3 November - Ability to attend the official Welcome Reception from 1700-1900 on Sunday, 3 November - A distinctive meeting badge that grants access to the venue (not to be used to attend working sessions) - Participation in a separate companion email list if you choose to help communicate and make plans with other IETF Companions. You can register your companion at any time via the IETF website or onsite at the meeting. To join the 88 companions mailing list only see: https://www.ietf.org/mailman/listinfo/88companions 5. Social Event There will not be a social event at the IETF 88 in Vancouver. Only 30 days until the Vancouver IETF!
WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
A new IETF working group has been proposed in the Internet Area. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg at ietf.org) by 2013-10-10. Extensions for Scalable DNS Service Discovery (dnssd) Current Status: Proposed WG Chairs: Ralph Droms rdroms.i...@gmail.com Tim Chown t...@ecs.soton.ac.uk Assigned Area Director: Ted Lemon ted.le...@nominum.com Mailing list Address: dnssd...@ietf.org To Subscribe: dnssdext-requ...@ietf.org Archive: http://www.ietf.org/mail-archive/web/dnssdext Charter: Background -- Zero configuration networking protocols are currently well suited to discover services within the scope of a single link. In particular, the DNS-SD [RFC 6763] and mDNS [RFC6762] protocol suite (sometimes referred to using Apple Computer Inc.'s trademark, Bonjour) are widely used for DNS-based service discovery and host name resolution on a single link. The DNS-SD/mDNS protocol suite is used in many scenarios including home, campus, and enterprise networks. However, the zero configuration mDNS protocol is constrained to link-local multicast scope by design, and therefore cannot be used to discover services on remote links. In a home network that consists of a single (possibly bridged) link, users experience the expected discovery behavior; available services appear because all devices share a common link. However, in multi-link home networks (as envisaged by the homenet WG) or in routed campus or enterprise networks, devices and users can only discover services on the same link, which is a significant limitation. This has led to calls, such as the Educause petition, to develop an appropriate service discovery solution to span multiple links or to perform discovery across a wide area, not necessarily on directly connected links. In addition, the Smart Energy Profile 2 Application Protocol Standard, published by ZigBee Alliance and HomePlug Powerline Alliance specifies the DNS-SD/mDNS protocol suite as the basis for its method of zero configuration service discovery. However, its use of wireless mesh multi-link subnets in conjunction with traditional routed networks will require extensions to the DNS-SD/mDNS protocols to allow operation across multiple links. The scenarios in which multi-link service discovery is required may be zero configuration environments, environments where administrative configuration is supported, or a mixture of the two. As demand for service discovery across wider area routed networks grows, some vendors are beginning to ship proprietary solutions. It is thus both timely and important that efforts to develop improved, scalable, autonomous service discovery solutions for routed networks are coordinated towards producing a single, standards-based solution. The WG will consider the tradeoffs between reusing/extending existing protocols and developing entirely new ones. It is highly desirable that any new solution is backwardly compatible with existing DNS-SD/mDNS deployments. Any solution developed by the dnssd WG must not conflict or interfere with the operation of other zero-configuration service and naming protocols such as uPnP or LLMNR. Integration with such protocols is out of scope for this WG. The focus of the WG is to develop a solution for extended, scalable DNS-SD. This work is likely to highlight problems and challenges with naming protocols, as some level of coexistence will be required between local zero configuration name services and those forming part of the global DNS. It is important that these issues are captured and documented for further analysis; solving those problems is however not within the scope of this WG. Working Group Description - To that end, the primary goals of the dnssd WG are as follows: 1. To document a set of requirements for scalable, autonomous DNS-based service discovery in routed, multi-link networks in the following five scenarios: (A) Personal Area networks, e.g., one laptop and one printer. This is the simplest example of a service discovery network, and may or may not have external connectivity. (B) Home networks, as envisaged by the homenet WG, consisting of one or more exit routers, with one or more upstream providers or networks, and an arbitrary internal topology with heterogeneous media where routing is automatically configured. The home network would typically be a single zero configuration administrative domain with a relatively limited number of devices. (C) Wireless 'hotspot' networks, which may include wireless networks made available in public places, or temporary or permanent infrastructures targeted towards meeting or conference style events, e.g., as
Re: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
Discussion of IETF consensus activities is supposed to occur on the IETF mailing list, not on the working group mailing list, which doesn't yet exist. We'll set up the new mailing list when the working group is approved. Sorry for the confusion.
Re: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
On Oct 3, 2013, at 3:05 PM, manning bill bmann...@isi.edu wrote: but the To Subscribe pointer is busted…. Correct. I should have gotten the information right before sending out the announcement, but I blew it—sorry about that.
IETF 88 Preliminary Agenda Delayed
The publishing of the preliminary agenda has been delayed due to issues with integrating the new agenda tool into the datatracker. We hope to have these issues resolved by Friday, October 4th, and will post the preliminary agenda as soon as possible. We appreciate your patience as we work to resolve these challenges. Sincerely, The IETF Secretariat