From owner-ipdvb@erg.abdn.ac.uk Fri Oct 1 08:57:29 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i917u9bH005153 for ; Fri, 1 Oct 2004 08:56:09 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i917u91P005152 for ipdvb-subscribed-users; Fri, 1 Oct 2004 08:56:09 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from [10.0.1.53] (maxp17.abdn.ac.uk [139.133.7.176]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i917t0m7005114 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT) for ; Fri, 1 Oct 2004 08:55:03 +0100 (BST) User-Agent: Microsoft-Entourage/11.0.0.040405 Date: Fri, 01 Oct 2004 08:55:18 +0100 Subject: Re: IETF-61 Preparations (November 7-12, 2004) From: Gorry Fairhurst To: Message-ID: In-Reply-To: <098001c4a723$12a2a740$ad02a8c0@copernicus> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk Yikes time is running out - You have to publish the document as an individual draft I need to do a WG Call to adopt, I can give my blessing, on the basis of the charter and then assuming the call to adopt goes OK, you can submit as a WG draft. On 30/9/04 8:23 pm, "Marie-Jose Montpetit" wrote: > Does that mean that if I submit AR next week it could become a WG document? > > Marie-Jose > ----- Original Message ----- > From: "Gorry Fairhurst" > To: > Sent: Thursday, September 30, 2004 1:58 PM > Subject: IETF-61 Preparations (November 7-12, 2004) > > >> >> Please note that all WG participants are invited to the next IETF >> meeting to be held in Washington DC. Details of the meeting and >> hotel/meeting regsitration information may be found at: >> >> http://www.ietf.org/meetings/IETF-61.html >> >> >> The ipdvb WG is scheduled to meet during this IETF meeting and has been >> allocated a 2 hour slot within the Agenda (NOTE: the timing of >> individual WG meetings is provisional at this stage). >> >> Some important dates for prospective Internet Draft authors are: >> >> October 11, Monday >> - WG Chair approval for initial WG document (Version -00) submission >> >> October 18, Monday >> - Internet Draft Cut-off for initial document (-00) submission >> >> October 25, Monday - Internet Draft final submission cut-off >> >> October 27, Wednesday - Pre-Registration and Pre-payment cut-off >> >> November 1, Monday - Working Group agendas due >> >> November 7-12, 2004 - 61st IETF Meeting in Washington, DC, USA >> >> >> Could anyone who wishes to submit an ID which may be of interest to the >> ipdvb community please tell me as soon as possible! >> >> Best wishes, >> >> Gorry Fairhurst >> ipdvb WG Chair >> >> > From owner-ipdvb@erg.abdn.ac.uk Fri Oct 1 08:51:35 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i917oG8K004999 for ; Fri, 1 Oct 2004 08:50:16 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i917oFQU004998 for ipdvb-subscribed-users; Fri, 1 Oct 2004 08:50:16 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from [10.0.1.53] (maxp17.abdn.ac.uk [139.133.7.176]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i917musT004950 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT) for ; Fri, 1 Oct 2004 08:49:02 +0100 (BST) User-Agent: Microsoft-Entourage/11.0.0.040405 Date: Fri, 01 Oct 2004 08:49:18 +0100 Subject: I-D ACTION:draft-ietf-ipdvb-arch-01.txt From: Gorry Fairhurst To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over DVB Working Group of the IETF. Title : A Framework for transmission of IP datagrams over MPEG-2 Networks Author(s) : M. Montpetit, et al. Filename : draft-ietf-ipdvb-arch-01.txt Pages : 39 Date : 2004-9-30 This document describes an architecture for the transport of IP Datagrams over ISO MPEG-2 Transport Streams (TS). The MPEG-2 TS has been widely accepted not only for providing digital TV services, but also as a subnetwork technology for building IP networks. Examples of systems using MPEG-2 include the Digital Video Broadcast (DVB) and Advanced Television Systems Committee (ATSC) Standards for Digital Television. The document identifies the need for a set of Internet standards defining the interface between the MPEG-2 Transport Stream and an IP subnetwork. It suggests a new encapsulation method for IP datagrams and proposes protocols to perform IPv6/IPv4 address resolution, to associate IP packets with the properties of the Logical Channels provided by an MPEG-2 TS. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipdvb-arch-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request at ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipdvb-arch-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv at ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipdvb-arch-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ I-D-Announce mailing list I-D-Announce at ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce From owner-ipdvb@erg.abdn.ac.uk Mon Oct 4 17:42:17 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i94GfNsY024369 for ; Mon, 4 Oct 2004 17:41:23 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i94GfNBp024368 for ipdvb-subscribed-users; Mon, 4 Oct 2004 17:41:23 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i94Ge7bS024328 for ; Mon, 4 Oct 2004 17:40:08 +0100 (BST) Received: from copernicus ([141.149.180.247]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041004164005.XGUQ24594.out001.verizon.net@copernicus> for ; Mon, 4 Oct 2004 11:40:05 -0500 Message-ID: <00d301c4aa30$e060d110$ad02a8c0@copernicus> From: "Marie-Jose Montpetit" To: Subject: Use of XML for MPEG Network config Date: Mon, 4 Oct 2004 12:40:30 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00CC_01C4AA0F.5552AF10" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [141.149.180.247] at Mon, 4 Oct 2004 11:39:59 -0500 X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk This is a multi-part message in MIME format. ------=_NextPart_000_00CC_01C4AA0F.5552AF10 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable List: I am putting together a short draft for the next IETF on the use of XML = for MPEG network configuration. This is part of the extension work of a = larger IP Over DVB ESA sponsored study as well as my other R&D = activities. The poster child right now is address resolution as this is part of the = WG charter, but I can see this approach as being useful for a larger set = of application. Our initial view is to have 3 types of services: - a static version based on local configuration that can be accessed via = the web - a subscriber service - on demand service We expect to be able to use the same semantics and have investigated = transport methods based on SIP, SOAP/UDP and SOAP/SIP. I know we are not = probably the only people on the list thinking about this as the above IP = mechanisms for network control are fairly popular right now. I welcome comments or real life implementations of this. Thanks Marie-Jose ------=_NextPart_000_00CC_01C4AA0F.5552AF10 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
List:
 
I am putting together a short draft for = the next=20 IETF on the use of XML for MPEG network configuration. This is part of = the=20 extension work of a larger IP Over DVB ESA sponsored study as well as my = other=20 R&D activities.
 
The poster child right now is address = resolution as=20 this is part of the WG charter, but I can see this approach as = being useful=20 for a larger set of application. Our initial view is to have 3 types of=20 services:
- a static version based on local = configuration=20 that can be accessed via the web
- a subscriber service
- on demand service
We expect to be able to use the same = semantics and=20 have investigated transport methods based on SIP, SOAP/UDP and SOAP/SIP. = I know=20 we are not probably the only people on the list thinking about this as = the above=20 IP mechanisms for network control are fairly popular right = now.
 
I welcome comments or real life = implementations of=20 this.
 
Thanks
 
Marie-Jose
 
 
 
------=_NextPart_000_00CC_01C4AA0F.5552AF10-- From owner-ipdvb@erg.abdn.ac.uk Tue Oct 5 15:31:34 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i95EUWqv018503 for ; Tue, 5 Oct 2004 15:30:32 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i95EUWhw018502 for ipdvb-subscribed-users; Tue, 5 Oct 2004 15:30:32 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from nando.org (adsl-068-213-247-068.sip.mia.bellsouth.net [68.213.247.68]) by erg.abdn.ac.uk (8.12.11/8.12.11) with SMTP id i95ESH2E018414 for ; Tue, 5 Oct 2004 15:28:18 +0100 (BST) Date: Tue, 05 Oct 2004 10:26:01 -0500 To: "Ip-dvb" From: "Clausen" Subject: Re: Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--------avrpswqgqtdvhgniokoq" X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-SpamScore: ssss X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk ----------avrpswqgqtdvhgniokoq Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit >The snake


:)

----------avrpswqgqtdvhgniokoq Content-Type: image/bmp; name="oykybxlaye.bmp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="oykybxlaye.bmp" Content-ID: Qk0+BwAAAAAAADYAAAAoAAAAPAAAAA8AAAABABAAAAAAAAgHAAAAAAAAAAAA AAAAAAAAAAAA/3//f/9//3//f/9//3//f/9//3//f/9/XwhfCF8IXwhfCF8I XwhfCF8IXwhfCF8IXwhfCF8IXwhfCF8IXwhfCF8IXwhfCF8IXwhfCF8IXwhf CF8IXwhfCF8IXwhfCP9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9//3//f/9/fy1fCN97/3//f/9/n1JfCN85X2v/f/9/33tfSl8Iv1b/f/9/ /3+/d985Xwi/Vv9//3//f/9//39/LV8I33v/f/9//3//f/9//3//f/9//3// f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/X0pfCJ9z /3//f79WXwifcx9jXwifc/9/n1JfCL933zmfUv9//38fQl8IX2tfCL9W/3// f/9//39fSl8In3P/f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9/fy1fCF8IXwhfCF8IH0L/f38tXwj/f997Xwif Uv9/XwhfCP9/31pfCL93/39fCF8I/39fCH8t/39/LV8IXwhfCF8IXwgfQv9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9/n1JfCJ9zX2tfCJ9S/3//f18IXwj/f/9/XwhfCP9/XwhfCP9/X2tfCN9a /3/fOV8I/39fCF8I/3+fUl8In3Nfa18In1L/f/9//3//f/9//3//f/9//3// f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/33t/Ld85v3dfCB9C /3//f18IXwh/b/9/XwhfCP9/XwhfCP9/n3NfCF9K/39fa18IX2tfCB9C/3/f e38t3zm/d18IH0L/f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9//39/b18IP2dfCF8I/3//f985XwhfSp9zXwif Uv9/X0pfCJ9z33tfCF8I/3//f39vXwhfCN9a/3//f39vXwg/Z18IXwj/f/9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9//3//f99afy3fOV8In3P/f79WXwifUn8tX0rfe/9/H2NfCF9r/39fCF8I /3//f19KXwifc18I31r/f/9/31p/Ld85Xwifc/9//3//f/9//3//f/9//3// f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/H0JfCF8I X2v/f39vXwgfY/9//3//f/9/33tfCN9a/39fCF8I/3//f18IXwj/f18IXwj/ f/9//38fQl8IXwhfa/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9//3//f/9/v3d/LV8IH2P/f/9/X0rfOd97Xwjf Of9//3+/Vt85v3dfCJ9S/3//f19KXwifc18I3zn/f/9//3+/d38tXwgfY/9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9//3//f/9//39fa18IX0r/f/9//3+fUl8Ify1fa/9//3//f79WXwhfSt97 /3//f/9/X0pfCN85v3f/f/9//3//f19rXwhfSv9//3//f/9//3//f/9//3// f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/ /3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3// f/9//3//f/9/ ----------avrpswqgqtdvhgniokoq Content-Type: application/octet-stream; name="Dog.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Dog.zip" ----------avrpswqgqtdvhgniokoq-- From owner-ipdvb@erg.abdn.ac.uk Wed Oct 6 12:29:34 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96BRrOu012300 for ; Wed, 6 Oct 2004 12:27:53 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i96BRrih012299 for ipdvb-subscribed-users; Wed, 6 Oct 2004 12:27:53 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from erg.abdn.ac.uk (gresley.erg.abdn.ac.uk [139.133.207.106]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96BQcK8012260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 6 Oct 2004 12:26:40 +0100 (BST) Message-ID: <4163D66F.6050107@erg.abdn.ac.uk> Date: Wed, 06 Oct 2004 12:26:39 +0100 From: Gorry Fairhurst Organization: Univesrity of Aberdeen User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ipdvb@erg.abdn.ac.uk Subject: Re: Use of XML for MPEG Network config References: <00d301c4aa30$e060d110$ad02a8c0@copernicus> In-Reply-To: <00d301c4aa30$e060d110$ad02a8c0@copernicus> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk I agree that XML is now becoming a common configuration language, and this is certainly one way we must explore in the ipdvb WG: both for setting up the L1/L2 information at the Receivers and IP Gateways and also for address resolution. It would be interesting to explore alternatives for the ways in which XML could be used to map IP addresses to PIDs. Can I ask everyone on this list to send an email if they know of any existing work (or work-in-progress), especially if it is relevant to MPEG-2 transmission networks? Thanks Marie-Jose for starting this topic, and offering to write a draft! Gorry Marie-Jose Montpetit wrote: > List: > > I am putting together a short draft for the next IETF on the use of XML > for MPEG network configuration. This is part of the extension work of a > larger IP Over DVB ESA sponsored study as well as my other R&D activities. > > The poster child right now is address resolution as this is part of the > WG charter, but I can see this approach as being useful for a larger set > of application. Our initial view is to have 3 types of services: > - a static version based on local configuration that can be accessed via > the web > - a subscriber service > - on demand service > We expect to be able to use the same semantics and have investigated > transport methods based on SIP, SOAP/UDP and SOAP/SIP. I know we are not > probably the only people on the list thinking about this as the above IP > mechanisms for network control are fairly popular right now. > > I welcome comments or real life implementations of this. > > Thanks > > Marie-Jose > > > From owner-ipdvb@erg.abdn.ac.uk Wed Oct 6 13:18:01 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96CGHxc013521 for ; Wed, 6 Oct 2004 13:16:17 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i96CGHNr013520 for ipdvb-subscribed-users; Wed, 6 Oct 2004 13:16:17 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from informatik.uni-bremen.de (imh.informatik.uni-bremen.de [134.102.224.4]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96CEUfV013458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 6 Oct 2004 13:14:31 +0100 (BST) Received: (from jo@localhost) by informatik.uni-bremen.de (8.12.11/8.12.11) id i96CEQdP028046; Wed, 6 Oct 2004 14:14:26 +0200 (MEST) From: Joerg Ott Message-Id: <200410061214.i96CEQdP028046@informatik.uni-bremen.de> Subject: Re: Use of XML for MPEG Network config To: ipdvb@erg.abdn.ac.uk Date: Wed, 6 Oct 2004 14:14:26 +0200 (MEST) Cc: jo@Informatik.Uni-Bremen.DE (Joerg Ott) In-Reply-To: <4163D66F.6050107@erg.abdn.ac.uk> from "Gorry Fairhurst" at Oct 06, 2004 12:26:39 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk Regarding XML, it would be great if we could first formulate the problem and then figure out whether XML is an adequate solution. That said, there is some work ongoing in the IETF that could be relevant here (that actually uses XML): the NETCONF WG http://www.ietf.org/html.charters/netconf-charter.html. I haven't followed the work in the Ops area that much though. Joerg > I agree that XML is now becoming a common configuration language, and > this is certainly one way we must explore in the ipdvb WG: both for > setting up the L1/L2 information at the Receivers and IP Gateways and > also for address resolution. It would be interesting to explore > alternatives for the ways in which XML could be used to map IP addresses > to PIDs. > > Can I ask everyone on this list to send an email if they know of any > existing work (or work-in-progress), especially if it is relevant to > MPEG-2 transmission networks? > > Thanks Marie-Jose for starting this topic, and offering to write a draft! > > Gorry > > Marie-Jose Montpetit wrote: > > > List: > > > > I am putting together a short draft for the next IETF on the use of XML > > for MPEG network configuration. This is part of the extension work of a > > larger IP Over DVB ESA sponsored study as well as my other R&D activities. > > > > The poster child right now is address resolution as this is part of the > > WG charter, but I can see this approach as being useful for a larger set > > of application. Our initial view is to have 3 types of services: > > - a static version based on local configuration that can be accessed via > > the web > > - a subscriber service > > - on demand service > > We expect to be able to use the same semantics and have investigated > > transport methods based on SIP, SOAP/UDP and SOAP/SIP. I know we are not > > probably the only people on the list thinking about this as the above IP > > mechanisms for network control are fairly popular right now. > > > > I welcome comments or real life implementations of this. > > > > Thanks > > > > Marie-Jose > > > > > > > From owner-ipdvb@erg.abdn.ac.uk Wed Oct 6 14:56:23 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96DseSH015729 for ; Wed, 6 Oct 2004 14:54:40 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i96Dse7S015728 for ipdvb-subscribed-users; Wed, 6 Oct 2004 14:54:40 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from nab.org (foxtrot.nab.org [209.116.240.194]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96DrrAN015689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 6 Oct 2004 14:53:54 +0100 (BST) Received: from ([199.29.3.1]) by maildc2.nab.org with ESMTP id 4028857.2309380; Wed, 06 Oct 2004 09:53:14 -0400 Received: by mail.NAB.ORG with Internet Mail Service (5.5.2653.19) id ; Wed, 6 Oct 2004 09:53:14 -0400 Message-ID: <5A659834E1607E4EBD72FCE2FE5C9CF108EDC578@mail.NAB.ORG> From: "Allison, Art" To: "'ipdvb@erg.abdn.ac.uk'" Cc: "Jones, Graham" , "Mark Richer (E-mail)" Subject: RE: Use of XML for MPEG Network config Date: Wed, 6 Oct 2004 09:53:12 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk Gorry The ATSC has developed a XML-based standard for use in managing the System Information for MPEG2 transports. The initial release is focused on setting variables of the ATSC Program and System Information Protocol and maintaining consistency with the MPEG2 PAT/PMT structures. It was made available for public comment during the development cycle as document CS/75 http://www.atsc.org/standards/candidate_standards.html and it is now in the formal approval process. Is this the type of document you are seeking? Art ::{)> Arthur W. Allison Director, Science & Technology National Association of Broadcasters 202 429 5418 -----Original Message----- From: Gorry Fairhurst [mailto:gorry@erg.abdn.ac.uk] Sent: Wednesday, October 06, 2004 7:27 AM To: ipdvb@erg.abdn.ac.uk Subject: Re: Use of XML for MPEG Network config I agree that XML is now becoming a common configuration language, and this is certainly one way we must explore in the ipdvb WG: both for setting up the L1/L2 information at the Receivers and IP Gateways and also for address resolution. It would be interesting to explore alternatives for the ways in which XML could be used to map IP addresses to PIDs. Can I ask everyone on this list to send an email if they know of any existing work (or work-in-progress), especially if it is relevant to MPEG-2 transmission networks? Thanks Marie-Jose for starting this topic, and offering to write a draft! Gorry Marie-Jose Montpetit wrote: > List: > > I am putting together a short draft for the next IETF on the use of XML > for MPEG network configuration. This is part of the extension work of a > larger IP Over DVB ESA sponsored study as well as my other R&D activities. > > The poster child right now is address resolution as this is part of the > WG charter, but I can see this approach as being useful for a larger set > of application. Our initial view is to have 3 types of services: > - a static version based on local configuration that can be accessed via > the web > - a subscriber service > - on demand service > We expect to be able to use the same semantics and have investigated > transport methods based on SIP, SOAP/UDP and SOAP/SIP. I know we are not > probably the only people on the list thinking about this as the above IP > mechanisms for network control are fairly popular right now. > > I welcome comments or real life implementations of this. > > Thanks > > Marie-Jose > > > From owner-ipdvb@erg.abdn.ac.uk Wed Oct 6 15:37:26 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96EZO0v017022 for ; Wed, 6 Oct 2004 15:35:24 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i96EZOSA017021 for ipdvb-subscribed-users; Wed, 6 Oct 2004 15:35:24 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96EYl5c016991 for ; Wed, 6 Oct 2004 15:34:48 +0100 (BST) Received: from copernicus ([141.157.185.100]) by out005.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041006143448.UNLM24464.out005.verizon.net@copernicus>; Wed, 6 Oct 2004 09:34:48 -0500 Message-ID: <053301c4abb1$a9f4f2a0$ad02a8c0@copernicus> From: "Marie-Jose Montpetit" To: "Allison, Art" Cc: , "Jones, Graham" , "Mark Richer \(E-mail\)" References: <5A659834E1607E4EBD72FCE2FE5C9CF108EDC578@mail.NAB.ORG> Subject: Re: Use of XML for MPEG Network config Date: Wed, 6 Oct 2004 10:34:54 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [141.157.185.100] at Wed, 6 Oct 2004 09:34:20 -0500 X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk I had a quick look and yes this is very related to what we are doing. You obviously have done all the schema work for a wider range of configuration parameters. We have focussed on AR and have defined another much shorter list. Are your schemas public? What is the status of the standard? One thing we are also looking at is the distribution of the information. Does ATSC have the intention of standardising on that too? Marie-Jose ----- Original Message ----- From: "Allison, Art" To: Cc: "Jones, Graham" <>; "Mark Richer (E-mail)" <> Sent: Wednesday, October 06, 2004 9:53 AM Subject: RE: Use of XML for MPEG Network config > Gorry > The ATSC has developed a XML-based standard for use in managing the System > Information for MPEG2 transports. The initial release is focused on setting > variables of the ATSC Program and System Information Protocol and > maintaining consistency with the MPEG2 PAT/PMT structures. It was made > available for public comment during the development cycle as document CS/75 > http://www.atsc.org/standards/candidate_standards.html > and it is now in the formal approval process. Is this the type of document > you are seeking? > > Art > ::{)> > Arthur W. Allison > Director, Science & Technology > National Association of Broadcasters > 202 429 5418 > > -----Original Message----- > From: Gorry Fairhurst [mailto:gorry@erg.abdn.ac.uk] > Sent: Wednesday, October 06, 2004 7:27 AM > To: ipdvb@erg.abdn.ac.uk > Subject: Re: Use of XML for MPEG Network config > > > > I agree that XML is now becoming a common configuration language, and > this is certainly one way we must explore in the ipdvb WG: both for > setting up the L1/L2 information at the Receivers and IP Gateways and > also for address resolution. It would be interesting to explore > alternatives for the ways in which XML could be used to map IP addresses > to PIDs. > > Can I ask everyone on this list to send an email if they know of any > existing work (or work-in-progress), especially if it is relevant to > MPEG-2 transmission networks? > > Thanks Marie-Jose for starting this topic, and offering to write a draft! > > Gorry > > Marie-Jose Montpetit wrote: > > > List: > > > > I am putting together a short draft for the next IETF on the use of XML > > for MPEG network configuration. This is part of the extension work of a > > larger IP Over DVB ESA sponsored study as well as my other R&D activities. > > > > The poster child right now is address resolution as this is part of the > > WG charter, but I can see this approach as being useful for a larger set > > of application. Our initial view is to have 3 types of services: > > - a static version based on local configuration that can be accessed via > > the web > > - a subscriber service > > - on demand service > > We expect to be able to use the same semantics and have investigated > > transport methods based on SIP, SOAP/UDP and SOAP/SIP. I know we are not > > probably the only people on the list thinking about this as the above IP > > mechanisms for network control are fairly popular right now. > > > > I welcome comments or real life implementations of this. > > > > Thanks > > > > Marie-Jose > > > > > > > From owner-ipdvb@erg.abdn.ac.uk Wed Oct 6 15:52:28 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96EojF5017480 for ; Wed, 6 Oct 2004 15:50:45 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i96Eoj24017479 for ipdvb-subscribed-users; Wed, 6 Oct 2004 15:50:45 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from GWOUT.thalesgroup.com (gwout.thalesgroup.com [195.101.39.227]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96EnU90017429 for ; Wed, 6 Oct 2004 15:49:30 +0100 (BST) Received: from thalescan.corp.thales (200.3.2.3) by GWOUT.thalesgroup.com (NPlex 6.5.026) id 4163E92B00002498 for ipdvb@erg.abdn.ac.uk; Wed, 6 Oct 2004 14:52:52 +0200 Received: from lowplex.mut.thales ([10.33.19.4]) by thalescan with InterScan Messaging Security Suite; Wed, 06 Oct 2004 14:38:56 +0200 Received: from cnfplex.thomcast.thomson-csf.com (178.1.4.1) by lowplex.mut.thales (NPlex 6.5.026) id 415F72CF000B0C87 for ipdvb@erg.abdn.ac.uk; Wed, 6 Oct 2004 14:38:56 +0200 Received: from zethos.thomcast.thomson-csf.com (178.3.2.15) by cnfplex.thomcast.thomson-csf.com (NPlex 6.5.026) id 4160EDF70000400E for ipdvb@erg.abdn.ac.uk; Wed, 6 Oct 2004 14:38:51 +0200 Received: from thales-bm.com (178.3.1.71) by zethos.thomcast.thomson-csf.com (NPlex 6.5.026) id 414111470002272D for ipdvb@erg.abdn.ac.uk; Wed, 6 Oct 2004 14:41:03 +0200 Message-ID: <4163E8E2.FF636661@thales-bm.com> Date: Wed, 06 Oct 2004 14:45:22 +0200 From: Richard Lhermitte Organization: Thales Broadcast & Multimedia X-Mailer: Mozilla 4.78 [fr] (Windows NT 5.0; U) X-Accept-Language: fr MIME-Version: 1.0 To: ipdvb@erg.abdn.ac.uk Subject: Re: Use of XML for MPEG Network config References: <00d301c4aa30$e060d110$ad02a8c0@copernicus> <4163D66F.6050107@erg.abdn.ac.uk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk If it's just mapping IP addresses to PIDs, DVB has defined a specific table: INT (IP Notification Table). But this table does not inform about service types, service description and services schedule, but it could be possible to add some specific descriptors to this tables to give additional information about the IP stream contents. It depends on the information you would like to transmit in this “XML” description. Richard Gorry Fairhurst a écrit : > I agree that XML is now becoming a common configuration language, and > this is certainly one way we must explore in the ipdvb WG: both for > setting up the L1/L2 information at the Receivers and IP Gateways and > also for address resolution. It would be interesting to explore > alternatives for the ways in which XML could be used to map IP addresses > to PIDs. > > Can I ask everyone on this list to send an email if they know of any > existing work (or work-in-progress), especially if it is relevant to > MPEG-2 transmission networks? > > Thanks Marie-Jose for starting this topic, and offering to write a draft! > > Gorry > > Marie-Jose Montpetit wrote: > > > List: > > > > I am putting together a short draft for the next IETF on the use of XML > > for MPEG network configuration. This is part of the extension work of a > > larger IP Over DVB ESA sponsored study as well as my other R&D activities. > > > > The poster child right now is address resolution as this is part of the > > WG charter, but I can see this approach as being useful for a larger set > > of application. Our initial view is to have 3 types of services: > > - a static version based on local configuration that can be accessed via > > the web > > - a subscriber service > > - on demand service > > We expect to be able to use the same semantics and have investigated > > transport methods based on SIP, SOAP/UDP and SOAP/SIP. I know we are not > > probably the only people on the list thinking about this as the above IP > > mechanisms for network control are fairly popular right now. > > > > I welcome comments or real life implementations of this. > > > > Thanks > > > > Marie-Jose > > > > > > From owner-ipdvb@erg.abdn.ac.uk Wed Oct 6 16:15:48 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96FEloT018326 for ; Wed, 6 Oct 2004 16:14:47 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i96FElUg018325 for ipdvb-subscribed-users; Wed, 6 Oct 2004 16:14:47 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from out004.verizon.net (out004pub.verizon.net [206.46.170.142]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96FDY3n018282 for ; Wed, 6 Oct 2004 16:13:35 +0100 (BST) Received: from copernicus ([141.149.185.76]) by out004.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041006151334.VSTG28868.out004.verizon.net@copernicus> for ; Wed, 6 Oct 2004 10:13:34 -0500 Message-ID: <055001c4abb7$22eae200$ad02a8c0@copernicus> From: "Marie-Jose Montpetit" To: References: <00d301c4aa30$e060d110$ad02a8c0@copernicus> <4163D66F.6050107@erg.abdn.ac.uk> <4163E8E2.FF636661@thales-bm.com> Subject: Re: Use of XML for MPEG Network config Date: Wed, 6 Oct 2004 11:13:54 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [141.149.185.76] at Wed, 6 Oct 2004 10:13:31 -0500 X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk We are aware of INT (see the AR draft) but are looking yes at sending much more information. Marie-Jose ----- Original Message ----- From: "Richard Lhermitte" To: Sent: Wednesday, October 06, 2004 8:45 AM Subject: Re: Use of XML for MPEG Network config > If it's just mapping IP addresses to PIDs, DVB has defined a specific table: INT > (IP Notification Table). > But this table does not inform about service types, service description and > services schedule, but it could be possible to add some specific descriptors to > this tables to give additional information about the IP stream contents. It > depends on the information you would like to transmit in this "XML" description. > > Richard > > > > > Gorry Fairhurst a écrit : > > > I agree that XML is now becoming a common configuration language, and > > this is certainly one way we must explore in the ipdvb WG: both for > > setting up the L1/L2 information at the Receivers and IP Gateways and > > also for address resolution. It would be interesting to explore > > alternatives for the ways in which XML could be used to map IP addresses > > to PIDs. > > > > Can I ask everyone on this list to send an email if they know of any > > existing work (or work-in-progress), especially if it is relevant to > > MPEG-2 transmission networks? > > > > Thanks Marie-Jose for starting this topic, and offering to write a draft! > > > > Gorry > > > > Marie-Jose Montpetit wrote: > > > > > List: > > > > > > I am putting together a short draft for the next IETF on the use of XML > > > for MPEG network configuration. This is part of the extension work of a > > > larger IP Over DVB ESA sponsored study as well as my other R&D activities. > > > > > > The poster child right now is address resolution as this is part of the > > > WG charter, but I can see this approach as being useful for a larger set > > > of application. Our initial view is to have 3 types of services: > > > - a static version based on local configuration that can be accessed via > > > the web > > > - a subscriber service > > > - on demand service > > > We expect to be able to use the same semantics and have investigated > > > transport methods based on SIP, SOAP/UDP and SOAP/SIP. I know we are not > > > probably the only people on the list thinking about this as the above IP > > > mechanisms for network control are fairly popular right now. > > > > > > I welcome comments or real life implementations of this. > > > > > > Thanks > > > > > > Marie-Jose > > > > > > > > > > > From owner-ipdvb@erg.abdn.ac.uk Wed Oct 6 18:51:05 2004 Received: from mavis.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96HoLCn021546 for ; Wed, 6 Oct 2004 18:50:21 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i96HoLmw021545 for ipdvb-subscribed-users; Wed, 6 Oct 2004 18:50:21 +0100 (BST) X-Authentication-Warning: mavis.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from nab.org (foxtrot.nab.org [209.116.240.194]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i96HnmIs021524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 6 Oct 2004 18:49:50 +0100 (BST) Received: from ([199.29.3.1]) by maildc2.nab.org with ESMTP id 4028857.2313153; Wed, 06 Oct 2004 13:49:16 -0400 Received: by mail.NAB.ORG with Internet Mail Service (5.5.2653.19) id ; Wed, 6 Oct 2004 13:49:16 -0400 Message-ID: <5A659834E1607E4EBD72FCE2FE5C9CF108EDC584@mail.NAB.ORG> From: "Allison, Art" To: "'Marie-Jose Montpetit'" , "Allison, Art" Cc: ipdvb@erg.abdn.ac.uk, "Jones, Graham" , "Mark Richer (E-mail)" Subject: RE: Use of XML for MPEG Network config Date: Wed, 6 Oct 2004 13:49:09 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-ERG-MailScanner: Found to be clean, Found to be clean Sender: owner-ipdvb@erg.abdn.ac.uk Precedence: bulk Reply-To: ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-From: owner-ipdvb@erg.abdn.ac.uk X-ERG-MailScanner-To: ipdvb-subscribed-users@mavis.erg.abdn.ac.uk Expect a more detailed response to your questions in a day or two from Mr. Jones. ATSC Standards are provided free of charge. Art ::{)> Arthur W. Allison Director, Science & Technology National Association of Broadcasters 202 429 5418 -----Original Message----- From: Marie-Jose Montpetit [mailto:mariejose.montpetit@verizon.net] Sent: Wednesday, October 06, 2004 10:35 AM To: Allison, Art Cc: ipdvb@erg.abdn.ac.uk; Jones, Graham; Mark Richer (E-mail) Subject: Re: Use of XML for MPEG Network config I had a quick look and yes this is very related to what we are doing. You obviously have done all the schema work for a wider range of configuration parameters. We have focussed on AR and have defined another much shorter list. Are your schemas public? What is the status of the standard? One thing we are also looking at is the distribution of the information. Does ATSC have the intention of standardising on that too? Marie-Jose ----- Original Message ----- From: "Allison, Art" To: Cc: "Jones, Graham" <>; "Mark Richer (E-mail)" <> Sent: Wednesday, October 06, 2004 9:53 AM Subject: RE: Use of XML for MPEG Network config > Gorry > The ATSC has developed a XML-based standard for use in managing the System > Information for MPEG2 transports. The initial release is focused on setting > variables of the ATSC Program and System Information Protocol and > maintaining consistency with the MPEG2 PAT/PMT structures. It was made > available for public comment during the development cycle as document CS/75 > http://www.atsc.org/standards/candidate_standards.html > and it is now in the formal approval process. Is this the type of document > you are seeking? > > Art > ::{)> > Arthur W. Allison > Director, Science & Technology > National Association of Broadcasters > 202 429 5418 > > -----Original Message----- > From: Gorry Fairhurst [mailto:gorry@erg.abdn.ac.uk] > Sent: Wednesday, October 06, 2004 7:27 AM > To: ipdvb@erg.abdn.ac.uk > Subject: Re: Use of XML for MPEG Network config > > > > I agree that XML is now becoming a common configuration language, and > this is certainly one way we must explore in the ipdvb WG: both for > setting up the L1/L2 information at the Receivers and IP Gateways and > also for address resolution. It would be interesting to explore > alternatives for the ways in which XML could be used to map IP addresses > to PIDs. > > Can I ask everyone on this list to send an email if they know of any > existing work (or work-in-progress), especially if it is relevant to > MPEG-2 transmission networks? > > Thanks Marie-Jose for starting this topic, and offering to write a draft! > > Gorry > > Marie-Jose Montpetit wrote: > > > List: > > > > I am putting together a short draft for the next IETF on the use of XML > > for MPEG network configuration. This is part of the extension work of a > > larger IP Over DVB ESA sponsored study as well as my other R&D activities. > > > > The poster child right now is address resolution as this is part of the > > WG charter, but I can see this approach as being useful for a larger set > > of application. Our initial view is to have 3 types of services: > > - a static version based on local configuration that can be accessed via > > the web > > - a subscriber service > > - on demand service > > We expect to be able to use the same semantics and have investigated > > transport methods based on SIP, SOAP/UDP and SOAP/SIP. I know we are not > > probably the only people on the list thinking about this as the above IP > > mechanisms for network control are fairly popular right now. > > > > I welcome comments or real life implementations of this. > > > > Thanks > > > > Marie-Jose > > > > > > >