IETF Logo Mail Archive

Re: [Netconf] IETF Last Call Gen-ART review of draft-ietf-netconf-restconf-15

Martin Bjorklund <mbj@tail-f.com> Sun, 25 September 2016 15:33 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB9B12B237 for <netconf@ietfa.amsl.com>; Sun, 25 Sep 2016 08:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.217
X-Spam-Level:
X-Spam-Status: No, score=-4.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCiFbOWoPFV2 for <netconf@ietfa.amsl.com>; Sun, 25 Sep 2016 08:33:51 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 52FAE12B226 for <netconf@ietf.org>; Sun, 25 Sep 2016 08:33:51 -0700 (PDT)
Received: from localhost (h-85-226.a165.priv.bahnhof.se [94.254.85.226]) by mail.tail-f.com (Postfix) with ESMTPSA id 91EE41AE028F; Sun, 25 Sep 2016 17:33:48 +0200 (CEST)
Date: Sun, 25 Sep 2016 17:33:48 +0200
Message-Id: <20160925.173348.1439815720507640241.mbj@tail-f.com>
To: andy@yumaworks.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <CABCOCHTmxNNrGopELX=w+XvG2Q=NoxrxEzJ0OzJ3o2yyxTDCLA@mail.gmail.com>
References: <87zinbq4ai.fsf@hobgoblin.ariadne.com> <CABCOCHTmxNNrGopELX=w+XvG2Q=NoxrxEzJ0OzJ3o2yyxTDCLA@mail.gmail.com>
X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/WgZwlj_iZTZZCzhLKAG_ztAYLLg>
Cc: netconf@ietf.org
Subject: Re: [Netconf] IETF Last Call Gen-ART review of draft-ietf-netconf-restconf-15
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Sep 2016 15:33:53 -0000

Andy Bierman <andy@yumaworks.com> wrote:
> On Tue, Sep 13, 2016 at 7:10 AM, Dale R. Worley <worley@ariadne.com> wrote:
> >     - Does XRD (RFC 6415) admit relative links as values of the href
> >     attribute of the Link element?  Relative links are not usually
> >     considered to be "URIs", but rather "URI-references" (RFC 3986 section
> >     4.1), and RFC 6415 uses "URI" consistently, not "URI-reference".
> >     Also, all examples in RFC 6415 show complete URIs.  If the href
> >     attributes have to be full URIs, then the problem with host
> >     identifiers described above also arises.
> >
> > This issue doesn't seem to have been addressed at all in the draft,
> > though I have a vague memory of discussion of using templates as an
> > alternative.  But all of the XRD examples seem to be incorrect in that
> > they use relative URIs as values of the href attribute.
> >
> 
> 
> I asked Kent and Martin to research this issue

This seems to be a general RFC6415-problem, not specific to RESTCONF.
Anyway, the OASIS spec for XRD says that the "href" attribute is of
XSD type "anyURI", which allows relative links.


/martin

v2.23.0 | Report a Bug | By Email