IETF Logo Mail Archive

Re: [NFVCON] a side meeting @ IETF 89

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Sun, 23 February 2014 19:32 UTC

Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: nfvcon@ietfa.amsl.com
Delivered-To: nfvcon@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17DF81A06DF for <nfvcon@ietfa.amsl.com>; Sun, 23 Feb 2014 11:32:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 coYZmMzFZZNi for <nfvcon@ietfa.amsl.com>; Sun, 23 Feb 2014 11:32:34 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 9B4D51A06DB for <nfvcon@ietf.org>; Sun, 23 Feb 2014 11:32:33 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id s1NJWVZF001363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 23 Feb 2014 20:32:31 +0100
Received: from DEMUHTC001.nsn-intra.net ([10.159.42.32]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id s1NJWVDi010535 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 23 Feb 2014 20:32:31 +0100
Received: from DEMUHTC011.nsn-intra.net (10.159.42.42) by DEMUHTC001.nsn-intra.net (10.159.42.32) with Microsoft SMTP Server (TLS) id 14.3.123.3; Sun, 23 Feb 2014 20:32:31 +0100
Received: from DEMUMBX005.nsn-intra.net ([169.254.5.200]) by DEMUHTC011.nsn-intra.net ([10.159.42.42]) with mapi id 14.03.0123.003; Sun, 23 Feb 2014 20:32:31 +0100
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [NFVCON] a side meeting @ IETF 89
Thread-Index: Ac8uGjCORSOz84PWS6aWzeX9QW29xv//ziUAgAAXJID//sDOwIAFY9WA//7v6OCAAi1OAP//wSnA
Date: Sun, 23 Feb 2014 19:32:30 +0000
Message-ID: <E4DE949E6CE3E34993A2FF8AE79131F8290C3B@DEMUMBX005.nsn-intra.net>
References: <E33E01DFD5BEA24B9F3F18671078951F2482E117@nkgeml501-mbs.china.huawei.com> <77748736-91BD-4207-8C25-B304FB44308B@lucidvision.com> <53061E3F.4040200@gmail.com> <E33E01DFD5BEA24B9F3F18671078951F2482E436@nkgeml501-mbs.china.huawei.com> <0F95A18E-04EF-4382-B4E3-2815D89B7FF7@tid.es> <E4DE949E6CE3E34993A2FF8AE79131F8290080@DEMUMBX005.nsn-intra.net> <20140223164146.GA98040@elstar.local>
In-Reply-To: <20140223164146.GA98040@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.109]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1207
X-purgate-ID: 151667::1393183952-00005322-8A84C87F/0-0/0-0
Archived-At: http://mailarchive.ietf.org/arch/msg/nfvcon/27Gyju7z-TKzedAk7p9bTzGZJ-c
Cc: "nfvcon@ietf.org" <nfvcon@ietf.org>
Subject: Re: [NFVCON] a side meeting @ IETF 89
X-BeenThere: nfvcon@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "NFV \(Network Function Virtualization\) Configuration and Modeling" <nfvcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfvcon>, <mailto:nfvcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfvcon/>
List-Post: <mailto:nfvcon@ietf.org>
List-Help: <mailto:nfvcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfvcon>, <mailto:nfvcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Feb 2014 19:32:36 -0000

Juergen,

the result of the discussion was that RESTCONF is a protocol almost similar to NETCONF in terms of capabilities, to access YANG modules over HTTP, with REST characteristics but not RESTful. That said you can use it for configuration management.

> And who says this is useful or desirable?
I don't know what you are referring to.

Cheers, 
Mehmet 


> -----Original Message-----
> From: ext Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-
> university.de]
> Sent: Sunday, February 23, 2014 5:42 PM
> To: Ersue, Mehmet (NSN - DE/Munich)
> Cc: nfvcon@ietf.org
> Subject: Re: [NFVCON] a side meeting @ IETF 89
> 
> On Sun, Feb 23, 2014 at 03:05:17PM +0000, Ersue, Mehmet (NSN -
> DE/Munich) wrote:
> 
> > RESTCONF would be perfect in such an environment as it can support
> > HTML-based REST-like configuration.
> 
> What is heck is "HTML-based REST-like configuration"? And who says
> this is useful or desirable?
> 
> /js
> 
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

v2.23.0 | Report a Bug | By Email