[netmod] FW: DISCUSS: <draft-ietf-netmod-dsdl-map-09.txt>

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 21 October 2010 14:11 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: netmod@core3.amsl.com
Delivered-To: netmod@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CAB03A69FB for <netmod@core3.amsl.com>; Thu, 21 Oct 2010 07:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level:
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ynFfzGq2Yv-W for <netmod@core3.amsl.com>; Thu, 21 Oct 2010 07:11:36 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 196E53A6A1C for <netmod@ietf.org>; Thu, 21 Oct 2010 07:11:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,217,1286164800"; d="scan'208";a="213012362"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 21 Oct 2010 10:12:54 -0400
X-IronPort-AV: E=Sophos;i="4.58,217,1286164800"; d="scan'208";a="528723522"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 21 Oct 2010 10:12:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Oct 2010 16:12:37 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402664639@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: DISCUSS: <draft-ietf-netmod-dsdl-map-09.txt>
Thread-Index: ActxKBzLkGbGbIzlRZWhQwIePScQ1gAAcCyQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Ladislav Lhotka <lhotka@cesnet.cz>
Cc: netmod@ietf.org
Subject: [netmod] FW: DISCUSS: <draft-ietf-netmod-dsdl-map-09.txt>
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 14:11:40 -0000

Hi Lada,

Please address the issues raised by Sean in his DISCUSS. 

Thanks and Regards,

Dan


-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of Sean Turner
Sent: Thursday, October 21, 2010 3:57 PM
To: iesg@ietf.org
Cc: draft-ietf-netmod-dsdl-map@tools.ietf.org; netmod-chairs@tools.ietf.org
Subject: DISCUSS: <draft-ietf-netmod-dsdl-map-09.txt>

Discuss:
This is a discuss-discuss (I'm not asking for any changes - just trying to figure this out)

DSRL can change the validated schema.  The validated schema is the bit that normally would have been sent down the wire from say a client to a server.  From what I've yahoooo!-ed, DSRL can be used to modify the names of elements and fields.  Say a client changes the name of a field called "stop" to "arrêt" - who is the server going to know to undo that change to get back to a validated schema?  Are the all the mappings performed sent along from the client to the server to facilitate this?

The document includes the following text:

While the mapping from YANG to DSDL described in this document may in principle be invertible, the inverse mapping from DSDL to YANG is beyond the scope of this document.

Are we setting ourselves for clients who send stuff to servers and the server can't validate that the response is a validate schema?