[Netconf] Impacts of bcp56bis on RESTCONF?

otilibil@eurecom.fr Tue, 03 April 2018 10:48 UTC

Return-Path: <otilibil@eurecom.fr>
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 0A26A12E88C for <netconf@ietfa.amsl.com>; Tue, 3 Apr 2018 03:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 DCndNrO12vco for <netconf@ietfa.amsl.com>; Tue, 3 Apr 2018 03:48:14 -0700 (PDT)
Received: from smtp2.eurecom.fr (smtp2.eurecom.fr [193.55.113.211]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB08120726 for <netconf@ietf.org>; Tue, 3 Apr 2018 03:48:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.48,400,1517871600"; d="scan'208";a="7875122"
Received: from thorgal.eurecom.fr ([10.3.2.220]) by drago2i.eurecom.fr with ESMTP; 03 Apr 2018 12:48:10 +0200
Received: (from apache@localhost) by thorgal.eurecom.fr (8.14.4+Sun/8.14.4/Submit) id w33AmB0o007879 for netconf@ietf.org; Tue, 3 Apr 2018 12:48:11 +0200 (CEST)
X-Authentication-Warning: thorgal.eurecom.fr: apache set sender to otilibil@eurecom.fr using -f
Received: from reverse.completel.net (reverse.completel.net [92.103.89.82]) by webmail.eurecom.fr (Horde MIME library) with HTTP; Tue, 03 Apr 2018 12:48:11 +0200
Message-ID: <20180403124811.mbostbi1rswk8ock@webmail.eurecom.fr>
Date: Tue, 03 Apr 2018 12:48:11 +0200
From: otilibil@eurecom.fr
To: netconf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)
X-Originating-IP: 92.103.89.82
X-Remote-Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/neQ4NggCyirOyKF3tvE2IVk6grg>
Subject: [Netconf] Impacts of bcp56bis on RESTCONF?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 03 Apr 2018 10:48:17 -0000

Hello all,
HTTPbis is working on [bcp56bis]; which shall obsolete [RFC3205].  
RESTCONF being built on HTTP, I am wondering; will it be impacted by  
the new Best Practices?

Regards,
Ariel

[bcp56bis] https://tools.ietf.org/html/draft-ietf-httpbis-bcp56bis-03
[RFC3205] https://tools.ietf.org/html/rfc3205

-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr