References from draft-vanderstok-core-bc

This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
draft-cheshire-dnsext-dns-sd DNS-Based Service Discovery
Refs Ref'd by
Proposed Standard informatively references
draft-cheshire-dnsext-multicastdns Multicast DNS
Refs Ref'd by
Proposed Standard informatively references
draft-ietf-core-coap The Constrained Application Protocol (CoAP)
Refs Ref'd by
Proposed Standard informatively references
draft-ietf-core-link-format Constrained RESTful Environments (CoRE) Link Format
Refs Ref'd by
Proposed Standard informatively references
draft-lynn-core-discovery-mapping CoRE Link-Format to DNS-Based Service Discovery Mapping
Refs Ref'd by
informatively references
draft-lynn-dnsext-site-mdns Extended Multicast DNS
Refs Ref'd by
informatively references
draft-martocci-6lowapp-building-applications Commercial Building Applications Requirements
Refs Ref'd by
informatively references
draft-rahman-core-groupcomm Group Communication for CoAP
Refs Ref'd by
informatively references
draft-shelby-core-resource-directory CoRE Resource Directory
Refs Ref'd by
informatively references
draft-tolle-cap A UDP/IP Adaptation of the ZigBee Application Protocol
Refs Ref'd by
informatively references
RFC 1034 Domain names - concepts and facilities
Refs Ref'd by
Internet Standard normatively references
RFC 1123 Requirements for Internet Hosts - Application and Support
Refs Ref'd by
Internet Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
Refs Ref'd by
Draft Standard normatively references
RFC 2782 A DNS RR for specifying the location of services (DNS SRV)
Refs Ref'd by
Proposed Standard normatively references
RFC 3306 Unicast-Prefix-based IPv6 Multicast Addresses
Refs Ref'd by
Proposed Standard normatively references
RFC 3307 Allocation Guidelines for IPv6 Multicast Addresses
Refs Ref'd by
Proposed Standard normatively references
RFC 3596 DNS Extensions to Support IP Version 6
Refs Ref'd by
Internet Standard normatively references
RFC 3629 UTF-8, a transformation format of ISO 10646
Refs Ref'd by
Internet Standard normatively references
RFC 3956 Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address
Refs Ref'd by
Proposed Standard normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
Refs Ref'd by
Internet Standard normatively references
RFC 4944 Transmission of IPv6 Packets over IEEE 802.15.4 Networks
Refs Ref'd by
Proposed Standard normatively references
RFC 5198 Unicode Format for Network Interchange
Refs Ref'd by
Proposed Standard normatively references
RFC 5785 Defining Well-Known Uniform Resource Identifiers (URIs)
Refs Ref'd by
Proposed Standard normatively references
RFC 5790 Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) Protocols
Refs Ref'd by
Proposed Standard normatively references
STD 13 Domain names - implementation and specification
Refs Ref'd by
Internet Standard normatively references
STD 3 Requirements for Internet Hosts - Application and Support
Refs Ref'd by
Internet Standard normatively references
STD 63 UTF-8, a transformation format of ISO 10646
Refs Ref'd by
Internet Standard normatively references
STD 66 Uniform Resource Identifier (URI): Generic Syntax
Refs Ref'd by
Internet Standard normatively references