Skip to main content

Interconnecting Network Slice Subnets
draft-defoy-coms-subnet-interconnection-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Authors Xavier de Foy , Akbar Rahman
Last updated 2017-10-03
RFC stream (None)
Formats
Additional resources
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-defoy-coms-subnet-interconnection-00
Network Working Group                                      M. Nottingham
Internet-Draft                                           August 20, 2019
Obsoletes: 7320 (if approved)
Updates: 3986 (if approved)
Intended status: Best Current Practice
Expires: February 21, 2020

                        URI Design and Ownership
                     draft-nottingham-rfc7320bis-00

Abstract

   Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and
   extensible naming system wherein each scheme's specification may
   further restrict the syntax and semantics of identifiers using that
   scheme."  In other words, the structure of a URI is defined by its
   scheme.  While it is common for schemes to further delegate their
   substructure to the URI's owner, publishing independent standards
   that mandate particular forms of URI substructure is inappropriate,
   because that essentially usurps ownership.  This document further
   describes this problematic practice and provides some acceptable
   alternatives for use in standards.

Note to Readers

   _RFC EDITOR: please remove this section before publication_

   This is a proposed revision of RFC7320, aka BCP190.  The -00 draft is
   a copy of the published RFC; subsequent revisions will update it.

   The issues list for this draft can be found at
   https://github.com/mnot/I-D/labels/rfc7320 [1].

   The most recent (often, unpublished) draft is at
   https://mnot.github.io/I-D/rfc7320/ [2].

   Recent changes are listed at https://github.com/mnot/I-D/commits/gh-
   pages/rfc7320 [3].

   See also the draft's current status in the IETF datatracker, at
   https://datatracker.ietf.org/doc/draft-nottingham-rfc7320/ [4].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

Nottingham              Expires February 21, 2020               [Page 1]
Internet-Draft            URI Design Ownership               August 2019

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 21, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Intended Audience . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Notational Conventions  . . . . . . . . . . . . . . . . .   5
   2.  Best Current Practices for Standardizing Structured URIs  . .   5
     2.1.  URI Schemes . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  URI Authorities . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  URI Paths . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  URI Queries . . . . . . . . . . . . . . . . . . . . . . .   6
     2.5.  URI Fragment Identifiers  . . . . . . . . . . . . . . . .   7
   3.  Alternatives to Specifying Structure in URIs  . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
     6.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

Nottingham              Expires February 21, 2020               [Page 2]
Internet-Draft            URI Design Ownership               August 2019

amp; Rahman           Expires April 6, 2018                 [Page 6]
Internet-Draft               Network slicing                October 2017

Authors' Addresses

   Xavier de Foy
   InterDigital Inc.
   1000 Sherbrooke West
   Montreal
   Canada

   Email: Xavier.Defoy@InterDigital.com

   Akbar Rahman
   InterDigital Inc.
   1000 Sherbrooke West
   Montreal
   Canada

   Email: Akbar.Rahman@InterDigital.com

de Foy & Rahman           Expires April 6, 2018                 [Page 7]