
From david.kessens@nsn.com  Tue Nov  2 17:11:30 2010
Return-Path: <david.kessens@nsn.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 E3C0D3A6A53 for <netmod@core3.amsl.com>; Tue,  2 Nov 2010 17:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_46=0.6]
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 Pt2LANEKG0AR for <netmod@core3.amsl.com>; Tue,  2 Nov 2010 17:11:29 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 964043A68EC for <netmod@ietf.org>; Tue,  2 Nov 2010 17:11:29 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id oA30BX6o007523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <netmod@ietf.org>; Wed, 3 Nov 2010 01:11:33 +0100
Received: from localhost6.localdomain6 ([10.138.46.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id oA30BVlr028602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <netmod@ietf.org>; Wed, 3 Nov 2010 01:11:33 +0100
Received: from localhost6.localdomain6 (localhost.localdomain [127.0.0.1]) by localhost6.localdomain6 (8.14.4/8.14.4) with ESMTP id oA30C7pL008811 for <netmod@ietf.org>; Tue, 2 Nov 2010 17:12:07 -0700
Received: (from david@localhost) by localhost6.localdomain6 (8.14.4/8.14.4/Submit) id oA30C6lN008809 for netmod@ietf.org; Tue, 2 Nov 2010 17:12:06 -0700
X-Authentication-Warning: localhost6.localdomain6: david set sender to david.kessens@nsn.com using -f
Date: Tue, 2 Nov 2010 17:12:06 -0700
From: David Kessens <david.kessens@nsn.com>
To: netmod@ietf.org
Message-ID: <20101103001205.GM2038@nsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-08-17)
Subject: [netmod] Draft agenda for IETF 79
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: Wed, 03 Nov 2010 00:11:31 -0000

Hi,

Please see below for the first version of our agenda.

Please let us know if you are interested to present anything about our new
work items or whether there are topics that you would like to bring up for
discussion.

Thanks,

David Kessens & Juergen Schoenwaelder
---

Agenda (v1): NETMOD WG
Meeting:   IETF 79
Location:  Shangri-La Hotel Beijing, China
WG Chairs: David Kessens
	   Juergen Schoenwaelder
Jabber:    xmpp:netmod at jabber.ietf.org
WG URL:    http://tools.ietf.org/wg/netmod/


TUESDAY, November 9, 2010, 1300-1500, Meeting Room: Valley Ballroom A

1) Administrivia
   [chairs][ 5 min ]

   - minutes scribe     {volunteers welcome in advance!}
   - jabber scribe      {volunteers welcome in advance!}
   - blue sheets
   - agenda bashing


2) Work items from previous charter
   [chairs][ 10 min ]

   - Previously chartered working group items:
   
     RFC editor queue:
     - draft-ietf-netmod-arch-10 (waiting for draft-ietf-netconf-with-defaults)
     - draft-ietf-netmod-dsdl-map-10
     - draft-ietf-netmod-yang-usage-11
   
   - Published RFCs
     - RFC 6020 (draft-ietf-netmod-yang) 
     - RFC 6021 (draft-ietf-netmod-yang-types) 


3) New work items

   For each draft: if applicable, current status, delta from previous draft,
   open issues, and discussion.

   3.1 Core system data model

       Possible starting point:
       - draft-bierman-netconf-system-monitoring-00.txt
         Status: new submission
         (Andy Bierman)
   
   3.2 Core interface data model
   
       Martin Bjorklund is working on a concrete proposal for a base data
       model
   
   3.3 Core routing data model that can be augmented with routing protocol
       specifics.

       Ladislav Lhotka is looking at RPSL
   
   4.4 SMIv2 translation to YANG
   
       Possible starting point:
       - draft-schoenw-netmod-smi-yang-00.txt
         Status: expired, but possible work item for new charter
         Earlier presented slides:
         http://www.ietf.org/proceedings/78/slides/netmod-1.pdf 
         & 
         http://www.ietf.org/proceedings/75/slides/netmod-0.pdf
         (Juergen Schoenwaelder)

4) Other (non WG) Internet-Drafts, for feedback and discussion
   [chairs, we will only spend time on these items if we have time]

   - draft-bjorklund-netmod-snmp-cfg-00
     Status: new submission
     
   - draft-chen-netmod-yang-ext-00
     Status: new submission

   - draft-linowski-netmod-yang-abstract-04.txt
     Status: AD sponsored
     (Bernd Linowski)  


5) I/O with other WGs (NETCONF/IPFIX/others ?), activities this week
   [chairs]


6) A.O.B. and open mike
   [N.N.]
   {please identify issues in advance}

---

From dromasca@avaya.com  Thu Nov  4 03:34:12 2010
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 8DA7C3A692F for <netmod@core3.amsl.com>; Thu,  4 Nov 2010 03:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 UifhmIKj1rLT for <netmod@core3.amsl.com>; Thu,  4 Nov 2010 03:34:10 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 83BCC3A69F5 for <netmod@ietf.org>; Thu,  4 Nov 2010 03:34:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPco0kzGmAcF/2dsb2JhbAChdHGkCwKZE4VGBI12
X-IronPort-AV: E=Sophos;i="4.58,295,1286164800"; d="scan'208";a="248426031"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 04 Nov 2010 06:34:19 -0400
X-IronPort-AV: E=Sophos;i="4.58,295,1286164800"; d="scan'208";a="536524824"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Nov 2010 06:34:18 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 4 Nov 2010 11:34:10 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04026C3259@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AD review of draft-linowski-netmod-yang-abstract-04
Thread-Index: Act8C9FOIofpI/MZTfybBASmG4+nKg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <bernd.linowski@ext.nsn.com>, "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, <s.kuryla@gmail.com>
Cc: netmod@ietf.org
Subject: [netmod] AD review of draft-linowski-netmod-yang-abstract-04
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, 04 Nov 2010 10:34:12 -0000

I have reviewed draft-linowski-netmod-yang-abstract-04. I think that
this document is in good shape and I will proceed to sending it to IETF
Last Call. Please consider the comments below together with other IETF
Last Call comments.=20

The comments are marked with T for Technical and E for Editorial.=20


T1. As the intended status is Experimental, I believe that it would be
useful to add in the introduction some text that describes the purpose
of the experiment, and the fact that the language extensions described
in this document may become (if the experimental usage succeeds) either
a proposed standard or part of a future version of NETCONF.=20

T2. section 2.10 -  I do not understand the concept of equimentHolder -
is it the same as the vendor or manufacturer of a physical entity? Why
is it called differently?=20

T3. In the example in section 3.3=20

<serialNumeber>F-7786828</serialNumber>

What does a serial number mean for a physical link?=20


T4. In the IANA considerations section:=20

> Registrant Contact: The NETMOD WG of the IETF.

This is not a WG document. Did the WG formally agree to take upon this
role?=20

E1. idnits complains:

 =3D=3D Unused Reference: 'RFC5226' is defined on line 1364, but no =
explicit
reference was found in the text

E2. It would be good to mention explicitly relative to what are referred
the 'improvements' described in section 1.3

E3. I suggest that you reorder appendices and make the change log the
last one - paying attention to make changes in the places where the
other appendices are referred in the text. As the change log will be
taken out of the final version (I assume) this can avoid complications.=20

E4. Section 1.5.1:=20

>    It is
      important to notice that this kind of relationships do not mandate
      any particular location of the two connected hardware instances in
      any MIB. =20

Clarify what 'MIB' means here - MIB module, instance of MIB module?=20

E5. T3. In the example in section 3.3=20

<serialNumeber>F-7786828</serialNumber>

s/serialNumeber/serial/Number/


Thanks and Regards,

Dan



From j.schoenwaelder@jacobs-university.de  Tue Nov  9 18:58:19 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 1E01E3A67E5 for <netmod@core3.amsl.com>; Tue,  9 Nov 2010 18:58:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.037
X-Spam-Level: 
X-Spam-Status: No, score=-103.037 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, 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 qqCTcEfFE5Yq for <netmod@core3.amsl.com>; Tue,  9 Nov 2010 18:58:18 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 24A613A67DF for <netmod@ietf.org>; Tue,  9 Nov 2010 18:58:18 -0800 (PST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7C30AC001F; Wed, 10 Nov 2010 03:58:43 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id EHcERASQBETF; Wed, 10 Nov 2010 03:58:43 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id C3241C000B; Wed, 10 Nov 2010 03:58:42 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 5A9EC159C89D; Wed, 10 Nov 2010 03:58:42 +0100 (CET)
Date: Wed, 10 Nov 2010 03:58:42 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Dan Romascanu <dromasca@avaya.com>
Message-ID: <20101110025842.GB58773@elstar.local>
Mail-Followup-To: Dan Romascanu <dromasca@avaya.com>, David Kessens <david.kessens@nsn.com>, netmod@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: netmod@ietf.org
Subject: [netmod] netmod short meeting report
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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: Wed, 10 Nov 2010 02:58:19 -0000

Dan,

here is the short meeting report for NETMOD:

  The NETMOD working group was rechartered in October. During the WG
  meeting at the 79th IETF, the WG discussed some proposals of what the
  chartered core data models should include, how generic or specific
  they should be, how they should be structured, whether they should
  support network-wide data models etc. Some interested people are
  planning to meet later during the IETF week to produce perhaps
  consolidated input for the WG to review.  Some open issues for the
  SMIv2 to YANG translation were presented and closed. The individual
  I-D was accepted as the basis of the WG document (to be confirmed on
  the WG list).

/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/>

From mehmet.ersue@nsn.com  Fri Nov 26 02:33:35 2010
Return-Path: <mehmet.ersue@nsn.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 6BF6F3A6803 for <netmod@core3.amsl.com>; Fri, 26 Nov 2010 02:33:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.281
X-Spam-Level: 
X-Spam-Status: No, score=-102.281 tagged_above=-999 required=5 tests=[AWL=0.318, 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 cDrzKJUgpUME for <netmod@core3.amsl.com>; Fri, 26 Nov 2010 02:33:32 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id EEA0E3A6A5B for <netmod@ietf.org>; Fri, 26 Nov 2010 02:33:30 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id oAQAYTcc025084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Nov 2010 11:34:29 +0100
Received: from demuexc025.nsn-intra.net (demuexc025.nsn-intra.net [10.159.32.12]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id oAQAYNSe003555; Fri, 26 Nov 2010 11:34:29 +0100
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 26 Nov 2010 11:34:21 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Nov 2010 11:34:19 +0100
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6401484452@DEMUEXC006.nsn-intra.net>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04026C3259@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AD review of draft-linowski-netmod-yang-abstract-04
thread-index: Act8C9FOIofpI/MZTfybBASmG4+nKgRSOWNw
References: <EDC652A26FB23C4EB6384A4584434A04026C3259@307622ANEX5.global.avaya.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-OriginalArrivalTime: 26 Nov 2010 10:34:21.0375 (UTC) FILETIME=[7CAEACF0:01CB8D55]
Cc: s.kuryla@gmail.com, netmod@ietf.org
Subject: Re: [netmod] AD review of draft-linowski-netmod-yang-abstract-04
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: Fri, 26 Nov 2010 10:33:35 -0000

Hi Dan,

please find below our attempt to fix the issues you raised.

Mehmet


> -----Original Message-----
> From: ext Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Thursday, November 04, 2010 11:34 AM
> To: bernd.linowski@www.nokiasiemensnetworks.com; Ersue, Mehmet (NSN -
> DE/Munich); s.kuryla@gmail.com
> Cc: netmod@ietf.org
> Subject: AD review of draft-linowski-netmod-yang-abstract-04
>=20
> I have reviewed draft-linowski-netmod-yang-abstract-04. I think that
> this document is in good shape and I will proceed to sending it to
IETF
> Last Call. Please consider the comments below together with other IETF
> Last Call comments.
>=20
> The comments are marked with T for Technical and E for Editorial.
>=20
>=20
> T1. As the intended status is Experimental, I believe that it would be
> useful to add in the introduction some text that describes the purpose
> of the experiment, and the fact that the language extensions described
> in this document may become (if the experimental usage succeeds)
either
> a proposed standard or part of a future version of NETCONF.

We agree, we should add a sentence into the introduction section=20
stating, e.g.:=20
"After successful usage this experimental specification can be
republished=20
at IETF either as a proposed standard or as part of a future version of
YANG."
=20
> T2. section 2.10 -  I do not understand the concept of equimentHolder
-
> is it the same as the vendor or manufacturer of a physical entity? Why
> is it called differently?

The idea of making a distinction between "Equipment" and
"EquipmentHolders"
was taken over from SID. To my understanding, an equipment holder is
a piece of equipment with the primary purpose of containing other
equipment.
The description in SID V8 says:
"This class is based on the M.3100 specification, and is a base class
that represents physical objects
that are both manageable as well as able to host, hold, or contain other
physical objects.
Examples of physical objects that can be represented by instances of
this object class=20
are Racks, Chassis, Cards, and Slots."
=20
> T3. In the example in section 3.3
>=20
> <serialNumeber>F-7786828</serialNumber>
>=20
> What does a serial number mean for a physical link?

"serial number" could be the part number of a fiber link cable.=20
The SID describes serial number as "manufacturer-allocated part number",
so
in some cases this might also apply to physical links.
=20
>=20
> T4. In the IANA considerations section:
>=20
> > Registrant Contact: The NETMOD WG of the IETF.
>=20
> This is not a WG document. Did the WG formally agree to take upon this
> role?

We will note the document authors as Registrant Contact.
=20
> E1. idnits complains:
>=20
>  =3D=3D Unused Reference: 'RFC5226' is defined on line 1364, but no
> explicit
> reference was found in the text

The reference will be deleted.
=20
> E2. It would be good to mention explicitly relative to what are
> referred
> the 'improvements' described in section 1.3

We will note in section 1.3 that the improvements are compared to=20
languages without language abstractions.
=20
> E3. I suggest that you reorder appendices and make the change log the
> last one - paying attention to make changes in the places where the
> other appendices are referred in the text. As the change log will be
> taken out of the final version (I assume) this can avoid
complications.

OK.
=20
> E4. Section 1.5.1:
>=20
> >    It is
>       important to notice that this kind of relationships do not
> mandate
>       any particular location of the two connected hardware instances
> in
>       any MIB.
>=20
> Clarify what 'MIB' means here - MIB module, instance of MIB module?

It was meant to be the instances of a MIB module.
=20
> E5. T3. In the example in section 3.3
>=20
> <serialNumeber>F-7786828</serialNumber>
>=20
> s/serialNumeber/serial/Number/

Thanks for the hint.
=20
>=20
> Thanks and Regards,
>=20
> Dan
>=20

