idnits 2.17.1 draft-troan-homenet-naming-and-sd-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (October 15, 2012) is 4209 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force O. Troan 3 Internet-Draft Cisco 4 Intended status: Standards Track October 15, 2012 5 Expires: April 18, 2013 7 Naming and Service Discovery in the Home Network 8 draft-troan-homenet-naming-and-sd-00 10 Abstract 12 This memo describes how simple naming and service discovery is done 13 in the home network. 15 Status of this Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on April 18, 2013. 32 Copyright Notice 34 Copyright (c) 2012 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 3 51 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Problems and Requirements . . . . . . . . . . . . . . . . . . . 3 53 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 54 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 55 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 56 8. Normative References . . . . . . . . . . . . . . . . . . . . . 3 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 1. Introduction 61 2. Requirements Language 63 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 64 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 65 document are to be interpreted as described in RFC 2119 [RFC2119]. 67 3. Terminology 69 4. Problems and Requirements 71 5. Security Considerations 73 6. IANA Considerations 75 7. Acknowledgements 77 8. Normative References 79 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 80 Requirement Levels", BCP 14, RFC 2119, March 1997. 82 Author's Address 84 Ole Troan 85 Cisco 86 Oslo, 87 Norway 89 Email: ot@cisco.com