From owner-ipdvb@erg.abdn.ac.uk Wed Jun 2 09:16:25 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 i528Fod2026291 for ; Wed, 2 Jun 2004 09:15:50 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i528FoSg026290 for ipdvb-subscribed-users; Wed, 2 Jun 2004 09:15:50 +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.32] (maxp26.abdn.ac.uk [139.133.7.185]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i528FKrY026273 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 2 Jun 2004 09:15:22 +0100 (BST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Wed, 02 Jun 2004 09:15:40 +0100 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 Subject: A new revision of the requirements/framework draft 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 revision of the requirements/framework draft that was previously presented at the WG BoFs has been submitted as a new ID. This revision is a significant rewrite (with many new contributions). I will forward a copy of the announcement to the list soon, but here is a URL: http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-04.txt Best wishes, Gorry Fairhurst From owner-ipdvb@erg.abdn.ac.uk Wed Jun 2 10:11:12 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 i529ACpT028389 for ; Wed, 2 Jun 2004 10:10:13 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i529ACWf028388 for ipdvb-subscribed-users; Wed, 2 Jun 2004 10:10:12 +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.32] (maxp16.abdn.ac.uk [139.133.7.175]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5299iVl028361 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 2 Jun 2004 10:09:46 +0100 (BST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Wed, 02 Jun 2004 10:10:01 +0100 Subject: CORRECTION: A new revision of the requirements/framework draft -05 From: Gorry Fairhurst To: Message-ID: In-Reply-To: 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 On 2/6/04 9:15 am, "Gorry Fairhurst" wrote: > > A new revision of the requirements/framework draft that was previously > presented at the WG BoFs has been submitted as a new ID. This revision is a > significant rewrite (with many new contributions). I will forward a copy of > the announcement to the list soon, but here is a URL: > > http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-04.txt > > Best wishes, > > Gorry Fairhurst > Sorry, thanks to those who already spotted my mistake, the new rev is of course draft-fair-ipdvb-req-05.txt, that is ***05****. Until this is officially issued, the submitted version is available at: http://www.erg.abdn.ac.uk/ip-dvb/ids/draft-fair-ipdvb-req-05.txt Gorry Fairhurst. From owner-ipdvb@erg.abdn.ac.uk Wed Jun 2 14:17:07 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 i52DGB8x007217 for ; Wed, 2 Jun 2004 14:16:11 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i52DGAbJ007216 for ipdvb-subscribed-users; Wed, 2 Jun 2004 14:16:11 +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 i52DFRaD007177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 2 Jun 2004 14:15:28 +0100 (BST) Received: from ([199.29.3.1]) by maildc2.nab.org with ESMTP ; Wed, 02 Jun 2004 09:14:56 -0400 Received: by mail.NAB.ORG with Internet Mail Service (5.5.2653.19) id ; Wed, 2 Jun 2004 09:14:56 -0400 Message-ID: <5A659834E1607E4EBD72FCE2FE5C9CF102FEC251@mail.NAB.ORG> From: "Allison, Art" To: "'ipdvb@erg.abdn.ac.uk'" Subject: RE: CORRECTION: A new revision of the requirements/framework draf t -05 Date: Wed, 2 Jun 2004 09:14:53 -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 Updates to current versions for selected references: 12.1 Normative References [ISO-MPEG] ISO/IEC 13818-1:2000 "Information technology -- Generic coding of moving pictures and associated audio information: Systems", International Standards Organization (ISO). ... 12.2 Informative References [ATSC] A/53C, "ATSC Digital Television Standard", Advanced Television Systems Committee (ATSC), Doc. A/53C, 2004. [ATSC-DAT] A/90, "ATSC Data Broadcast Standard", Advanced Television Systems Committee (ATSC), Doc. A/090, 2000 [ATSC-G] A/54A, "Guide to the use of the ATSC Digital Television Standard", Advanced Television Systems Committee (ATSC), Doc. A/54A, 2003. [ATSC-PSIP-TC] A/65B, "Program and System Information Protocol for Terrestrial Broadcast and Cable", Advanced Television Systems Committee (ATSC), Doc. A/65B, 2003. .... delete the following entry as it is in Normative Reference section(corrected there) [ISO-MPEG] ISO/IEC DIS 13818-1 "Information technology -- Generic coding of moving pictures and associated audio information: Systems", International Standards Organization (ISO). ---delete above entry--- [ISO-VID] ISO/IEC 13818-2:1998 "Information technology -- Generic coding of moving pictures and associated audio information: Video", International Standards Organization (ISO). .... Art ::{)> Art Allison Director Advanced Engineering NAB 1771 N St NW Washington DC 20036 202 429 5418 -----Original Message----- From: Gorry Fairhurst [mailto:gorry@erg.abdn.ac.uk] Sent: Wednesday, June 02, 2004 5:10 AM To: ipdvb@erg.abdn.ac.uk Subject: CORRECTION: A new revision of the requirements/framework draft -05 On 2/6/04 9:15 am, "Gorry Fairhurst" wrote: > > A new revision of the requirements/framework draft that was previously > presented at the WG BoFs has been submitted as a new ID. This revision is a > significant rewrite (with many new contributions). I will forward a copy of > the announcement to the list soon, but here is a URL: > > http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-04.txt > > Best wishes, > > Gorry Fairhurst > Sorry, thanks to those who already spotted my mistake, the new rev is of course draft-fair-ipdvb-req-05.txt, that is ***05****. Until this is officially issued, the submitted version is available at: http://www.erg.abdn.ac.uk/ip-dvb/ids/draft-fair-ipdvb-req-05.txt Gorry Fairhurst. From owner-ipdvb@erg.abdn.ac.uk Fri Jun 4 15:43:04 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 i54EemG9025606 for ; Fri, 4 Jun 2004 15:40:48 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i54EemTk025605 for ipdvb-subscribed-users; Fri, 4 Jun 2004 15:40:48 +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 [139.133.207.163] (dhcp-207-163.erg.abdn.ac.uk [139.133.207.163]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i54Ed1NR025482 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 4 Jun 2004 15:39:02 +0100 (BST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Fri, 04 Jun 2004 09:03:28 +0100 Subject: I-D ACTION:draft-collini-ipdvb-xule-00.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. Title : Ultra Lightweight Encapsulation (ULE) Extension Header Author(s) : G. Fairhurst, et al. Filename : draft-collini-ipdvb-xule-00.txt Pages : 14 Date : 2004-6-1 This document proposes an extension format for the Ultra-Lightweight Encapsulation (ULE) protocol. The proposed method allows ULE to carry both optional (with an explicit extension length) and mandatory (with an implicit extension length) header information to assist in network/Receiver processing of a SNDU. These functions modify the behaviour of ULE, and introduce header processing operations that will simplify the addition of new headers. This Internet Draft is presented as a separate document to allow ipdvb working group discussion of the design trade-offs involved. If accepted, the techniques will be incorporated within a future revision of ULE. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-collini-ipdvb-xule-00.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-collini-ipdvb-xule-00.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-collini-ipdvb-xule-00.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://www.ietf.org/mailman/listinfo/i-d-announce From owner-ipdvb@erg.abdn.ac.uk Mon Jun 7 15:29: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 i57ERv2t027708 for ; Mon, 7 Jun 2004 15:27:57 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i57ERuNP027707 for ipdvb-subscribed-users; Mon, 7 Jun 2004 15:27:57 +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 thingmagic.com (mail.thingmagic.com [207.31.248.245]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i57EQwA4027665 for ; Mon, 7 Jun 2004 15:26:58 +0100 (BST) Received: from [24.61.30.237] (account margaret HELO [192.168.2.2]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 85883; Mon, 07 Jun 2004 10:25:28 -0400 Mime-Version: 1.0 X-Sender: margaret@mail.thingmagic.com Message-Id: Date: Mon, 7 Jun 2004 10:25:42 -0400 To: ip-dvb@erg.abdn.ac.uk From: Margaret Wasserman Subject: Fwd: RE: FW: General Request for Assignments (if-type) (Dost) Cc: Bert Wijnen Content-Type: text/plain; charset="us-ascii" ; format="flowed" 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 Hi All, This is not quite IPDVB-related, but this seems like the most likely place to reach DVB experts in the IETF... Do you have any comments on the attached request that IANA allocate two if-type values for (apparently) DVB-related protocols? Particularly, do you have any thoughts on whether these are proprietary or industry standard protocols? AFAIK, there is no problem with allocating these values, we are just trying to determine how they should be named. Please include Bert Wijnen in any responses, as he may not be subscribed to the IPDVB list. Thanks! Margaret >> >> -----Original Message----- >> >> From: Eddie C. Dost [mailto:ecd@atecom.com] >> >> Sent: Tuesday, February 03, 2004 2:17 AM >> >> To: IANA >> >> Subject: Re: FW: General Request for Assignments (if-type) (Dost) >> >> >> >> >> >> Dear IANA, >> >> >> >> let me try to clearify why we would like to register >> these if-types. >> >> >> >> The types dvbSpiIn and dvbSpiOut are not proprietary, >> these are the >> >> synchronous parallel interfaces described in DVB-PI or EN 50083-9. >> >> Our equipment supports these interfaces in some >> configurations. There >> >> are configuration with only input interfaces and >> configurations with >> >> only output interfaces. >> >> >> >> The equipment always uses these interfaces in High >> Quality Video over >> >> ATM applications, so for the input interface we take the >> MPEG of the >> >> DVB-SPI and put that into AAL1, for the output interface >> we take an >> >> AAL1 ATM stream and output that on the DVB-SPI interface. >> >> >> >> The interfaces themself comply to the DVB Standards. >> >> >> >> sdtiIn and sdtiOut interfaces are compliant to the standard >> >> SMPTE 305M-2000 (Society of Motion Picture and Television >> Engineers). >> >> >> >> These interfaces are used the same way as the DVB-SPI interfaces, >> >> namely input or output only, and for transport of High >> Quality Video >> >> over ATM. >> >> >> >> We would like to register these if-types to use them in our SNMP >> >> management for our systems. The if-types are free to be >> used by others >> >> for the same purpose. If there is a standard SMPTE or DVB MIB for >> >> management of DVB-ASI, DVB-SPI or SMPTE SDTI interface I would be >> >> glad to hear about. If you know such a standard, please send >> >> a reference >> >> to this, as it is not known to me at current. >> >> >> >> If you need further information, please feel free to contact me. >> >> >> >> Best regards, >> >> Christian Dost >> >> >> >> > Dear Christian, >> >> > >> >> > Our if-type experts have reviewed your application. >> >> > Comments are inline. >> >> > >> >> > Best regards, >> >> > >> >> > IANA >> >> > >> >> > -----Original Message----- >> >> > > From: ecd@atecom.com [mailto:ecd@atecom.com] >> >> > > Sent: Thursday, January 15, 2004 3:31 AM >> >> > > To: iana@iana.org; ecd@atecom.com >> >> > > Subject: General Request for Assignments >> >> > > >> >> > > >> >> > > Contact Name : >> >> > > Christian Dost >> >> > > >> >> > > Contact Email : >> >> > > ecd@atecom.com >> >> > > >> >> > >> >> > >> >> > > Type of Assignment : >> >> > > interface types: dvbSpiIn, dvbSpiOut, sdtiIn, sdtiOut >> >> > > >> >> > >> >> > This requester also should explain why he/she needs an >> >> > ifType for xxxIn and xxxOut and not one that can be used for >> >> > both in and out. >> >> > >> >> > > Registry : >> >> > > IANAifType-MIB >> >> > > >> >> > >> >> > >> >> > > Description : >> >> > > The requested interface type assignments are used in our >> >> > > Video over ATM devices together with the allready >> >> existing interfaces >> >> > > dvbAsiIn and dvbAsiOut. Please feel >> >> > > free to assign any free number for these interfaces. >> >> > > >> >> > So... >> >> > - it sounds as if it is a proprietary ifType. If so, we >> want to see >> >> > that expressed in the name. e.g. something aka: atecomDvbSpiIn >> >> > - If not, then we want to try to udnerstand how/why >> this is generic >> >> > and public. We want to understand it does not conflivt with >> >> > DVB standards. >> >> > - We would like to see some documentation that shows >> how this works >> >> > >> >> > >> >> > >> >> > > Additional Info : >> >> > > >> >> > >> >> >> >> Eddie C. Dost manager firmware >> >> ATecoM GmbH >> >> ecd@atecom.com >> >> Pascalstr. 67 >> >> Phone: +49 2408 9596 0 Fax: +49 2408 9596 900 >> >> D-52076 Aachen >> >> GSM: +49 172 9312808 >> >> Germany >> >> >> > From owner-ipdvb@erg.abdn.ac.uk Mon Jun 7 19:32:22 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 i57IV5Jf007037 for ; Mon, 7 Jun 2004 19:31:05 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i57IV51m007035 for ipdvb-subscribed-users; Mon, 7 Jun 2004 19:31:05 +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 relay1.mail2web.com (relay1.mail2web.com [168.144.1.81]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i57IUS2B006996 for ; Mon, 7 Jun 2004 19:30:29 +0100 (BST) Received: from M2W073.mail2web.com ([168.144.251.183]) by relay1.mail2web.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 7 Jun 2004 14:30:23 -0400 Message-ID: <260780-22004617183011939@M2W073.mail2web.com> X-Priority: 3 X-Originating-IP: 61.11.77.233 X-URL: http://mail2web.com/ From: "williams@calsoft.co.in" To: ipdvb@erg.abdn.ac.uk Subject: Comments on ULE extension header.... Date: Mon, 7 Jun 2004 14:30:11 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 X-OriginalArrivalTime: 07 Jun 2004 18:30:23.0674 (UTC) FILETIME=[7F0461A0:01C44CBD] X-ERG-MailScanner: Found to be clean, Found to be clean X-ERG-MailScanner-SpamScore: s Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by erg.abdn.ac.uk id i57IV39v007032 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 Thanks to Gorry for publishing the draft :) Few Comments Editorial : --------- In Section 2, Figure 1,2 and 3 D_bit is maked as ZERO. It should be ONE Figure 3, T2 and H2 are interchanged. Concept: --------- When we are talking about backward compatibility, it is better to have version number in the ULE, so across the version it is identified uniquely. In Optional headers, Wish to add Source mac address... In case of UDLR(RFC3077), during DTCP announcement, ULE can take the source mac i.e. FUMAC makes simple in address resolution. -UDLR is jst an example. otherthings are security filters can be implemented based on source MAC. -William -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . From owner-ipdvb@erg.abdn.ac.uk Tue Jun 8 12:09:50 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 i58B9EWv014708 for ; Tue, 8 Jun 2004 12:09:14 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i58B9Dqt014707 for ipdvb-subscribed-users; Tue, 8 Jun 2004 12:09:14 +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.40] (maxp29.abdn.ac.uk [139.133.7.188]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i58B8XtJ014666 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 8 Jun 2004 12:08:37 +0100 (BST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Tue, 08 Jun 2004 10:50:26 +0100 Subject: Re: Comments on ULE extension header.... From: Gorry Fairhurst To: CC: Bernhard Collini-Nocker Message-ID: In-Reply-To: <260780-22004617183011939@M2W073.mail2web.com> 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 On 7/6/04 7:30 pm, "williams@calsoft.co.in" wrote: > Thanks to Gorry for publishing the draft :) This was a work of many discussions among many people... > Few Comments > Editorial : > --------- > In Section 2, Figure 1,2 and 3 D_bit is maked as ZERO. It should be ONE > Figure 3, T2 and H2 are interchanged. > > Concept: > --------- > When we are talking about backward compatibility, it is better to have > version number in the ULE, so across the version it is identified uniquely. Yes - and this *could* have been in the ULE base header, but there are significant disadvantages too - additional capacity would consumed. My suggestion is to use one encapsulation method per PID (MPEG-2 TS logical channel) - if we do this other signaling protocols can associate a particular PID with a particular encapsulation method. The descriptors passed by the signaling protocol could also differentiate MPE from ULE. If we need a new format for ULE sometime in the future, we could use this method to identify this. Are you suggestion a new OPTIONAL extension to give the version of the ULE protocol? - How do you see the additional benefits of this? > In Optional headers, Wish to add Source mac address... In case of > UDLR(RFC3077), during DTCP announcement, ULE can take the source mac i.e. > FUMAC makes simple in address resolution. -UDLR is jst an example. > otherthings are security filters can be implemented based on source MAC. > Yes - this is true. We had a discussion on this topic at the Vienna BoF, and at that time I don't recall a need for a MAC source without a MAC destination address. If that is still the case, then maybe the bridging format extension would satisfy this requirement? Thoughts? > -William > > > -------------------------------------------------------------------- > mail2web - Check your email from the web at > http://mail2web.com/ . > Gorry Fairhurst > From owner-ipdvb@erg.abdn.ac.uk Tue Jun 8 13:04:59 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 i58C3KrV016912 for ; Tue, 8 Jun 2004 13:03:20 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i58C3K6C016911 for ipdvb-subscribed-users; Tue, 8 Jun 2004 13:03:20 +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 lin.calsoft.co.in ([203.129.222.68]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i58C18sA016827 for ; Tue, 8 Jun 2004 13:01:09 +0100 (BST) Received: from calsoftwilliam ([203.129.222.92]) by lin.calsoft.co.in (8.11.0/8.11.0) with ESMTP id i58BmDa11728; Tue, 8 Jun 2004 17:18:13 +0530 From: "William StanisLaus" To: Cc: "'Bernhard Collini-Nocker'" Subject: RE: Comments on ULE extension header.... Date: Tue, 8 Jun 2004 17:29:20 +0530 Organization: CalSoft Message-ID: <005601c44d50$0993a550$8c0210ac@calsoftwilliam> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal In-Reply-To: X-MailScanner: Found to be clean 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 Please see the comments inlined... -William. > -----Original Message----- > From: owner-ipdvb@erg.abdn.ac.uk > [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst > Sent: Tuesday, June 08, 2004 3:20 PM > To: ipdvb@erg.abdn.ac.uk > Cc: Bernhard Collini-Nocker > Subject: Re: Comments on ULE extension header.... > > > On 7/6/04 7:30 pm, "williams@calsoft.co.in" > wrote: > > > Thanks to Gorry for publishing the draft :) > > This was a work of many discussions among many people... > > > > Few Comments > > Editorial : > > --------- > > In Section 2, Figure 1,2 and 3 D_bit is maked as ZERO. It > should be ONE > > Figure 3, T2 and H2 are interchanged. > > > > Concept: > > --------- > > When we are talking about backward compatibility, it is > better to have > > version number in the ULE, so across the version it is > identified uniquely. > > Yes - and this *could* have been in the ULE base header, but there are > significant disadvantages too - additional capacity would consumed. > > My suggestion is to use one encapsulation method per PID > (MPEG-2 TS logical > channel) - if we do this other signaling protocols can associate a > particular PID with a particular encapsulation method. The > descriptors > passed by the signaling protocol could also differentiate MPE > from ULE. > If we need a new format for ULE sometime in the future, we > could use this > method to identify this. > > Are you suggestion a new OPTIONAL extension to give the > version of the ULE > protocol? - How do you see the additional benefits of this? > William> I suggest to have it as a Mandatory header, Since different version of implementation of ULE can be differenciated with a version number. Say for example, in ULE version 1 I have 4 Mandatory headers. And we decide to add 2 more Mandatory headers and come up with a new version of ULE. In that case, since we have added new mandatory header the older implementation will jst drop the packet/SNDU. BUT if you have an version number, we can make it backward compatibily based on version number and still process the packet/SNDU by avoiding those header processing and dropping the packets. > > In Optional headers, Wish to add Source mac address... In case of > > UDLR(RFC3077), during DTCP announcement, ULE can take the > source mac i.e. > > FUMAC makes simple in address resolution. -UDLR is jst an example. > > otherthings are security filters can be implemented based > on source MAC. > > > > Yes - this is true. > > We had a discussion on this topic at the Vienna BoF, and at > that time I > don't recall a need for a MAC source without a MAC > destination address. If > that is still the case, then maybe the bridging format extension would > satisfy this requirement? > > Thoughts? William> In case of UDLR, it is not a packet forwarding, the orginator of the packet is the FEED itself i.e. satellite terminal. My understand with bridged format packets is sending the ethernet packets along with L2 information in satellite network, i.e. L2 tunneling. In that you still have outer ULE and MPEG headers. Please correct if I'm wrong. > > > -William > > > > > > -------------------------------------------------------------------- > > mail2web - Check your email from the web at > > http://mail2web.com/ . > > > > Gorry Fairhurst > > > From owner-ipdvb@erg.abdn.ac.uk Tue Jun 8 16:55: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 i58Frgx2025404 for ; Tue, 8 Jun 2004 16:53:42 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i58FrfZK025403 for ipdvb-subscribed-users; Tue, 8 Jun 2004 16:53:41 +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.41] (maxp19.abdn.ac.uk [139.133.7.178]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i58FmQMK025239 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 8 Jun 2004 16:52:39 +0100 (BST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Tue, 08 Jun 2004 15:41:31 +0100 Subject: Re: Comments on ULE extension header.... From: Gorry Fairhurst To: CC: "'Bernhard Collini-Nocker'" Message-ID: In-Reply-To: <005601c44d50$0993a550$8c0210ac@calsoftwilliam> 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 On Ethernet bridging... On 8/6/04 12:59 pm, "William StanisLaus" wrote: > Please see the comments inlined... > > -William. > >> -----Original Message----- >> From: owner-ipdvb@erg.abdn.ac.uk >> [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst >> Sent: Tuesday, June 08, 2004 3:20 PM >> To: ipdvb@erg.abdn.ac.uk >> Cc: Bernhard Collini-Nocker >> Subject: Re: Comments on ULE extension header.... >> >> >> On 7/6/04 7:30 pm, "williams@calsoft.co.in" >> wrote: > > >>> In Optional headers, Wish to add Source mac address... In case of >>> UDLR(RFC3077), during DTCP announcement, ULE can take the >> source mac i.e. >>> FUMAC makes simple in address resolution. -UDLR is jst an example. >>> otherthings are security filters can be implemented based >> on source MAC. >>> >> >> Yes - this is true. >> >> We had a discussion on this topic at the Vienna BoF, and at >> that time I >> don't recall a need for a MAC source without a MAC >> destination address. If >> that is still the case, then maybe the bridging format extension would >> satisfy this requirement? >> >> Thoughts? > > > William> In case of UDLR, it is not a packet forwarding, the orginator > of the packet is the FEED itself i.e. satellite terminal. My understand > with bridged format packets is sending the ethernet packets along with > L2 information in satellite network, i.e. L2 tunneling. In that you > still have outer ULE and MPEG headers. > Please correct if I'm wrong. > So I'd guess if you wanted a source MAC address, an example is: I.e.: >> >>> -William >>> >>> >>> -------------------------------------------------------------------- >>> mail2web - Check your email from the web at >>> http://mail2web.com/ . >>> >> >> Gorry Fairhurst >>> >> > From owner-ipdvb@erg.abdn.ac.uk Tue Jun 8 16:56:46 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 i58Ft1Lu025471 for ; Tue, 8 Jun 2004 16:55:01 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i58Ft0mq025469 for ipdvb-subscribed-users; Tue, 8 Jun 2004 16:55:01 +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.41] (maxp19.abdn.ac.uk [139.133.7.178]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i58FmQMJ025239 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 8 Jun 2004 16:52:37 +0100 (BST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Tue, 08 Jun 2004 15:35:59 +0100 Subject: Re: Comments on ULE extension header.... From: Gorry Fairhurst To: CC: "'Bernhard Collini-Nocker'" Message-ID: In-Reply-To: <005601c44d50$0993a550$8c0210ac@calsoftwilliam> 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 More on version identification... On 8/6/04 12:59 pm, "William StanisLaus" wrote: > Please see the comments inlined... > > -William. > >> -----Original Message----- >> From: owner-ipdvb@erg.abdn.ac.uk >> [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst >> Sent: Tuesday, June 08, 2004 3:20 PM >> To: ipdvb@erg.abdn.ac.uk >> Cc: Bernhard Collini-Nocker >> Subject: Re: Comments on ULE extension header.... >> >> >> On 7/6/04 7:30 pm, "williams@calsoft.co.in" >> wrote: >> >>> Thanks to Gorry for publishing the draft :) >> >> This was a work of many discussions among many people... >> >> >>> Few Comments >>> Editorial : >>> --------- >>> In Section 2, Figure 1,2 and 3 D_bit is maked as ZERO. It >> should be ONE >>> Figure 3, T2 and H2 are interchanged. >>> >>> Concept: >>> --------- >>> When we are talking about backward compatibility, it is >> better to have >>> version number in the ULE, so across the version it is >> identified uniquely. >> >> Yes - and this *could* have been in the ULE base header, but there are >> significant disadvantages too - additional capacity would consumed. >> >> My suggestion is to use one encapsulation method per PID >> (MPEG-2 TS logical >> channel) - if we do this other signaling protocols can associate a >> particular PID with a particular encapsulation method. The >> descriptors >> passed by the signaling protocol could also differentiate MPE >> from ULE. >> If we need a new format for ULE sometime in the future, we >> could use this >> method to identify this. >> >> Are you suggestion a new OPTIONAL extension to give the >> version of the ULE >> protocol? - How do you see the additional benefits of this? >> > > > William> I suggest to have it as a Mandatory header, Since different > version of implementation of ULE can be differenciated with a version > number. > Say for example, in ULE version 1 I have 4 Mandatory headers. And we > decide to add 2 more Mandatory headers and come up with a new version of > ULE. In that case, since we have added new mandatory header the older > implementation will jst drop the packet/SNDU. BUT if you have an version > number, we can make it backward compatibily based on version number and > still process the packet/SNDU by avoiding those header processing and > dropping the packets. > This is the first time we've discussed the published XULE draft, but if I understand correctly, the MANDATORY EXTENSION is one that MUST be processed before a PDU is forwarded. It does NOT imply it MUST be implemented. In the future, more MANDATORY EXTENSION headers could be added - if there was a case for this - by simply allocating entries in the IANA registry after publishing an RFC that defines the new extension header syntax. Older systems simply can not process these headers and discard the PDU when they find an unrecognised MANDATORY type (and ignore any following parts of this SNDU). In contrast, unrecognised OPTIONAL extensions can be ignored, and don't require the encapsulated PDU to be discarded. Given these features, it seems that new extensions could be introduced if new optimisations/requirements emerge. > >> >>> -William >>> >>> >>> -------------------------------------------------------------------- >>> mail2web - Check your email from the web at >>> http://mail2web.com/ . >>> >> >> Gorry Fairhurst >>> >> > Gorry Fairhurst From owner-ipdvb@erg.abdn.ac.uk Wed Jun 9 05:17:06 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 i594GQOr022091 for ; Wed, 9 Jun 2004 05:16:26 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i594GQBp022090 for ipdvb-subscribed-users; Wed, 9 Jun 2004 05:16:26 +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 lin.calsoft.co.in ([203.129.222.68]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i594FdTm022053 for ; Wed, 9 Jun 2004 05:15:42 +0100 (BST) Received: from calsoftwilliam ([203.129.222.92]) by lin.calsoft.co.in (8.11.0/8.11.0) with ESMTP id i5942ha19105; Wed, 9 Jun 2004 09:32:43 +0530 From: "William StanisLaus" To: Cc: "'Bernhard Collini-Nocker'" Subject: RE: Comments on ULE extension header.... Date: Wed, 9 Jun 2004 09:43:53 +0530 Organization: CalSoft Message-ID: <000e01c44dd8$2e28d880$8c0210ac@calsoftwilliam> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: X-MailScanner: Found to be clean 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 Let me make it clear, CASE 1: ------- Satellite terminal has two interface Ethernet and DVB. The packet received from Ethernet has to be forwarded in DVB interface, in that case we choose to do in bridged format.. So just take the L2 information from Ethernet packet and encapsulate with ULE and MPEG2-TS, without modifying anything and forward the packet in satellite network. i.e. L2 Tunneling NOTE: In this, L2 is IEEE 802.3 Encapsulation, might contain LLC and SNAP as well. CASE 2a: ------- Satellite terminal has two interface Ethernet and DVB. The packet received from Ethernet has to be forwarded in DVB interface, but bridged format in ULE, the terminal strips out L2 information from Ethernet and adds new L2 information i.e. SOURCE MAC as terminal which forwards the packet, DEST MAC as the terminal to which the packet has to be forward ( immediate next hop ) and protocol type CASE 2b: ------- Satellite terminal orginating a packet i.e. in this case it is not a forwarder but a host. Example UDLR, DTCP announcement (HELLO packet). If we wish to bridge the packet, exactly like CASE 2a we have to bridge the packet. Question: -------- In both CASE 2a and 2b, we have protocol type, in Bridged information and ULE Protocol Type, so something can be saved and some processing overhead can be improved if we have a plain SOURCE MAC in direct ULE optional header. Thoughts?? -William. > -----Original Message----- > From: owner-ipdvb@erg.abdn.ac.uk > [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst > Sent: Tuesday, June 08, 2004 8:12 PM > To: ipdvb@erg.abdn.ac.uk > Cc: 'Bernhard Collini-Nocker' > Subject: Re: Comments on ULE extension header.... > > > On Ethernet bridging... > > On 8/6/04 12:59 pm, "William StanisLaus" > wrote: > > > Please see the comments inlined... > > > > -William. > > > >> -----Original Message----- > >> From: owner-ipdvb@erg.abdn.ac.uk > >> [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst > >> Sent: Tuesday, June 08, 2004 3:20 PM > >> To: ipdvb@erg.abdn.ac.uk > >> Cc: Bernhard Collini-Nocker > >> Subject: Re: Comments on ULE extension header.... > >> > >> > >> On 7/6/04 7:30 pm, "williams@calsoft.co.in" > >> wrote: > > > > > > > > >>> In Optional headers, Wish to add Source mac address... In case of > >>> UDLR(RFC3077), during DTCP announcement, ULE can take the > >> source mac i.e. > >>> FUMAC makes simple in address resolution. -UDLR is jst an example. > >>> otherthings are security filters can be implemented based > >> on source MAC. > >>> > >> > >> Yes - this is true. > >> > >> We had a discussion on this topic at the Vienna BoF, and at > >> that time I > >> don't recall a need for a MAC source without a MAC > >> destination address. If > >> that is still the case, then maybe the bridging format > extension would > >> satisfy this requirement? > >> > >> Thoughts? > > > > > > William> In case of UDLR, it is not a packet forwarding, > the orginator > > of the packet is the FEED itself i.e. satellite terminal. > My understand > > with bridged format packets is sending the ethernet packets > along with > > L2 information in satellite network, i.e. L2 tunneling. In that you > > still have outer ULE and MPEG headers. > > Please correct if I'm wrong. > > > > So I'd guess if you wanted a source MAC address, an example is: > > > > I.e.: > > > > > > >> > >>> -William > >>> > >>> > >>> > -------------------------------------------------------------------- > >>> mail2web - Check your email from the web at > >>> http://mail2web.com/ . > >>> > >> > >> Gorry Fairhurst > >>> > >> > > > From owner-ipdvb@erg.abdn.ac.uk Wed Jun 9 05:30:59 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 i594UNe3022563 for ; Wed, 9 Jun 2004 05:30:23 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i594UNYN022560 for ipdvb-subscribed-users; Wed, 9 Jun 2004 05:30: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 lin.calsoft.co.in ([203.129.222.68]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i594SHne022460 for ; Wed, 9 Jun 2004 05:28:18 +0100 (BST) Received: from calsoftwilliam ([203.129.222.92]) by lin.calsoft.co.in (8.11.0/8.11.0) with ESMTP id i594Ega21385; Wed, 9 Jun 2004 09:44:43 +0530 From: "William StanisLaus" To: Cc: "'Bernhard Collini-Nocker'" Subject: RE: Comments on ULE extension header.... Date: Wed, 9 Jun 2004 09:55:52 +0530 Organization: CalSoft Message-ID: <000f01c44dd9$da5349f0$8c0210ac@calsoftwilliam> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: X-MailScanner: Found to be clean 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 Well, I agree for Mandatory headers, it MUST not be implemented across the version. But Version number tracks the supported Mandatory headers for that release/version. Hence we can always quote the implementation with the version number. For any commercial Marketing, Feature sheet says about the MPE, and jst version number will imply any supported Mandatory header. Otherwise it should list all the Mandatory headers in the Feature Sheet. -William. > -----Original Message----- > From: owner-ipdvb@erg.abdn.ac.uk > [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst > Sent: Tuesday, June 08, 2004 8:06 PM > To: ipdvb@erg.abdn.ac.uk > Cc: 'Bernhard Collini-Nocker' > Subject: Re: Comments on ULE extension header.... > > > More on version identification... > > On 8/6/04 12:59 pm, "William StanisLaus" > wrote: > > > Please see the comments inlined... > > > > -William. > > > >> -----Original Message----- > >> From: owner-ipdvb@erg.abdn.ac.uk > >> [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst > >> Sent: Tuesday, June 08, 2004 3:20 PM > >> To: ipdvb@erg.abdn.ac.uk > >> Cc: Bernhard Collini-Nocker > >> Subject: Re: Comments on ULE extension header.... > >> > >> > >> On 7/6/04 7:30 pm, "williams@calsoft.co.in" > >> wrote: > >> > >>> Thanks to Gorry for publishing the draft :) > >> > >> This was a work of many discussions among many people... > >> > >> > >>> Few Comments > >>> Editorial : > >>> --------- > >>> In Section 2, Figure 1,2 and 3 D_bit is maked as ZERO. It > >> should be ONE > >>> Figure 3, T2 and H2 are interchanged. > >>> > >>> Concept: > >>> --------- > >>> When we are talking about backward compatibility, it is > >> better to have > >>> version number in the ULE, so across the version it is > >> identified uniquely. > >> > >> Yes - and this *could* have been in the ULE base header, > but there are > >> significant disadvantages too - additional capacity would consumed. > >> > >> My suggestion is to use one encapsulation method per PID > >> (MPEG-2 TS logical > >> channel) - if we do this other signaling protocols can associate a > >> particular PID with a particular encapsulation method. The > >> descriptors > >> passed by the signaling protocol could also differentiate MPE > >> from ULE. > >> If we need a new format for ULE sometime in the future, we > >> could use this > >> method to identify this. > >> > >> Are you suggestion a new OPTIONAL extension to give the > >> version of the ULE > >> protocol? - How do you see the additional benefits of this? > >> > > > > > > William> I suggest to have it as a Mandatory header, Since different > > version of implementation of ULE can be differenciated with > a version > > number. > > Say for example, in ULE version 1 I have 4 Mandatory headers. And we > > decide to add 2 more Mandatory headers and come up with a > new version of > > ULE. In that case, since we have added new mandatory header > the older > > implementation will jst drop the packet/SNDU. BUT if you > have an version > > number, we can make it backward compatibily based on > version number and > > still process the packet/SNDU by avoiding those header > processing and > > dropping the packets. > > > > > This is the first time we've discussed the published XULE > draft, but if I > understand correctly, the MANDATORY EXTENSION is one that > MUST be processed > before a PDU is forwarded. It does NOT imply it MUST be implemented. > > In the future, more MANDATORY EXTENSION headers could be > added - if there > was a case for this - by simply allocating entries in the > IANA registry > after publishing an RFC that defines the new extension header > syntax. Older > systems simply can not process these headers and discard the > PDU when they > find an unrecognised MANDATORY type (and ignore any following > parts of this > SNDU). > > In contrast, unrecognised OPTIONAL extensions can be ignored, > and don't > require the encapsulated PDU to be discarded. > > Given these features, it seems that new extensions could be > introduced if > new optimisations/requirements emerge. > > > > >> > >>> -William > >>> > >>> > >>> > -------------------------------------------------------------------- > >>> mail2web - Check your email from the web at > >>> http://mail2web.com/ . > >>> > >> > >> Gorry Fairhurst > >>> > >> > > > > Gorry Fairhurst > From owner-ipdvb@erg.abdn.ac.uk Wed Jun 9 17:43:49 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 i59GhImu018391 for ; Wed, 9 Jun 2004 17:43:18 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i59GhHIQ018390 for ipdvb-subscribed-users; Wed, 9 Jun 2004 17:43: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 erg.abdn.ac.uk (gresley-ipv6.erg.abdn.ac.uk [IPv6:2001:630:241:1:20a:95ff:fe7d:5f0c]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i59GgbBj018354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 9 Jun 2004 17:42:38 +0100 (BST) Message-ID: <40C73DFE.5050109@erg.abdn.ac.uk> Date: Wed, 09 Jun 2004 17:42:38 +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: I-D ACTION:draft-fair-ipdvb-req-05.txt 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 The following draft -05 isnow available in the ID archives. (This **is** the same as previously announced on this list - with the corrected version number, which should have have been -05). Gorrb ---- New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Requirements for transmission of IP datagrams over MPEG-2 networks Author(s) : G. Fairhurst, et al. Filename : draft-fair-ipdvb-req-05.txt Pages : 38 Date : 2004-6-8 This document describes a new framework 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-fair-ipdvb-req-05.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-fair-ipdvb-req-05.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-fair-ipdvb-req-05.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 Thu Jun 10 11:37:25 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 i5AAatdl028803 for ; Thu, 10 Jun 2004 11:36:55 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5AAas0X028801 for ipdvb-subscribed-users; Thu, 10 Jun 2004 11:36:54 +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-ipv6.erg.abdn.ac.uk [IPv6:2001:630:241:1:20a:95ff:fe7d:5f0c]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5AAZHUM028718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 10 Jun 2004 11:35:18 +0100 (BST) Message-ID: <40C83963.6050504@erg.abdn.ac.uk> Date: Thu, 10 Jun 2004 11:35:15 +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: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt 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 As WG chair, I request the ipdvb list to consider whether this WG is willing to adopt the following individual Internet Draft (ID) as a WG ID. By adopting an individual ID as a working group ID, this WG indicates that it intends to be develop this into an RFC, according to the WG charter. WG documents should no longer be regarded as the property of the individuals who originally authored them - the working group as a whole must decide how they are shaped, and to see the document to a successful conclusion. If adopted, the Internet Draft will be renamed to start with the filename draft-ietf-ipdvb..., and will be listed on the IETF web page for this WG. For this document an Editor will be appointed to author new text and assist in this process. --- A Framework for transmission of IP datagrams over MPEG-2 networks Document: draft-fair-ipdvb-req-05.txt http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-05.txt --- This is being proposed as Charter item No.1. http://www.ietf.org/html.charters/ipdvb-charter.html You are actively encouraged to send email to this WG, to help make the decision for adoption. Possible recommendations are: 1) Support for adoption as a working group draft under our Charter i.e. Recommend this Internet Draft to be used as the basis for developing an RFC by the ipdvb WG. 2) Request for non-adoption i.e. That there is alternative approaches to the problem, and that the current draft is not sufficiently developed / or correctly designed ipdvb WG 3) Out of scope i.e. you believe the document to be beyond the scope of the approved ipdvb WG charter. Emails on this topic should be sent to the ipdvb mailing list BEFORE 17th June 2004. Gorry Fairhurst (ipdvb WG Chair) From owner-ipdvb@erg.abdn.ac.uk Thu Jun 10 12:07:59 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 i5AB5nL8029931 for ; Thu, 10 Jun 2004 12:05:49 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5AB5mv5029930 for ipdvb-subscribed-users; Thu, 10 Jun 2004 12:05:49 +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 mail.technotrend.de ([217.89.68.3]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5AB3ftp029827 for ; Thu, 10 Jun 2004 12:03:41 +0100 (BST) Received: from zwinkauwee (gate.technotrend.de [217.89.68.2]) by mail.technotrend.de (8.11.6/9.12.7) with ESMTP id i5AB3fX24235 for ; Thu, 10 Jun 2004 13:03:41 +0200 Message-Id: <200406101103.i5AB3fX24235@mail.technotrend.de> From: "Frank Zwinkau" To: Subject: unsubscribe Date: Thu, 10 Jun 2004 13:03:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <40C83963.6050504@erg.abdn.ac.uk> Thread-Index: AcRO2epc1hh18nrxQtStB5lT5SpuLAAAH53A 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 unsubscribe Please remove me from this list. From owner-ipdvb@erg.abdn.ac.uk Thu Jun 10 12:29:31 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 i5ABRksU000839 for ; Thu, 10 Jun 2004 12:27:46 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5ABRjQK000836 for ipdvb-subscribed-users; Thu, 10 Jun 2004 12:27:46 +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 out011.verizon.net (out011pub.verizon.net [206.46.170.135]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5ABQEoW000776 for ; Thu, 10 Jun 2004 12:26:15 +0100 (BST) Received: from copernicus ([68.163.245.165]) by out011.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040610112614.NHGQ18566.out011.verizon.net@copernicus> for ; Thu, 10 Jun 2004 06:26:14 -0500 Message-ID: <003301c44edd$baff02b0$b502a8c0@copernicus> From: "Marie-Jose Montpetit" To: References: <40C83963.6050504@erg.abdn.ac.uk> Subject: Re: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt Date: Thu, 10 Jun 2004 07:25:55 -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 out011.verizon.net from [68.163.245.165] at Thu, 10 Jun 2004 06:26:08 -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 approve. I think we need established requiments to guide the WG. Marie-Jose ----- Original Message ----- From: "Gorry Fairhurst" To: Sent: Thursday, June 10, 2004 6:35 AM Subject: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt > As WG chair, I request the ipdvb list to consider whether this > WG is willing to adopt the following individual Internet Draft > (ID) as a WG ID. > > By adopting an individual ID as a working group ID, this WG > indicates that it intends to be develop this into an RFC, > according to the WG charter. WG documents should no longer > be regarded as the property of the individuals who originally > authored them - the working group as a whole must decide how > they are shaped, and to see the document to a successful > conclusion. > > If adopted, the Internet Draft will be renamed to start > with the filename draft-ietf-ipdvb..., and will be listed > on the IETF web page for this WG. For this document an Editor > will be appointed to author new text and assist in this process. > > --- > > A Framework for transmission of IP datagrams over MPEG-2 networks > Document: draft-fair-ipdvb-req-05.txt > http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-05.txt > > --- > > This is being proposed as Charter item No.1. > http://www.ietf.org/html.charters/ipdvb-charter.html > > You are actively encouraged to send email to this WG, > to help make the decision for adoption. > Possible recommendations are: > > 1) Support for adoption as a working group draft under our Charter > i.e. Recommend this Internet Draft to be used as the basis for > developing an RFC by the ipdvb WG. > > 2) Request for non-adoption > i.e. That there is alternative approaches to > the problem, and that the current draft is not sufficiently > developed / or correctly designed ipdvb WG > > 3) Out of scope > i.e. you believe the document to be beyond the scope of the > approved ipdvb WG charter. > > Emails on this topic should be sent to the ipdvb mailing list > BEFORE 17th June 2004. > > > Gorry Fairhurst > (ipdvb WG Chair) > > > > From owner-ipdvb@erg.abdn.ac.uk Fri Jun 11 07:30:51 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 i5B6TAPk011076 for ; Fri, 11 Jun 2004 07:29:10 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5B6T9Ym011074 for ipdvb-subscribed-users; Fri, 11 Jun 2004 07:29:10 +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 mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5B6Ro3Q010999 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for ; Fri, 11 Jun 2004 07:27:51 +0100 (BST) Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i5B6Rmd20525 for ; Fri, 11 Jun 2004 09:27:48 +0300 (EET DST) X-Scanned: Fri, 11 Jun 2004 09:27:14 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i5B6REsA012617 for ; Fri, 11 Jun 2004 09:27:14 +0300 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks001.ntc.nokia.com 00j8LRwJ; Fri, 11 Jun 2004 09:27:13 EEST Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i5B6R7H05492 for ; Fri, 11 Jun 2004 09:27:07 +0300 (EET DST) Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 11 Jun 2004 09:26:59 +0300 Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 11 Jun 2004 09:26:59 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt Date: Fri, 11 Jun 2004 09:26:59 +0300 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt Thread-Index: AcRO4zjYY7nchiWsSTK9/T5OhazRvQAmZufQ From: To: X-OriginalArrivalTime: 11 Jun 2004 06:26:59.0696 (UTC) FILETIME=[19E1EF00:01C44F7D] X-ERG-MailScanner: Found to be clean, Found to be clean Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by erg.abdn.ac.uk id i5B6T3iJ011069 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 The work item is already on the charter so, providing the WG chairs are fine with it, it makes sense to make this a WG I-D unless there are good objections. I have no objections. Cheers, Rod. > -----Original Message----- > From: owner-ipdvb@erg.abdn.ac.uk [mailto:owner-ipdvb@erg.abdn.ac.uk]On > Behalf Of ext Marie-Jose Montpetit > Sent: Thursday, June 10, 2004 2:26 PM > To: ipdvb@erg.abdn.ac.uk > Subject: Re: Call for the ipdvb WG to adopt: > draft-fair-ipdvb-req-05.txt > > > I approve. I think we need established requiments to guide the WG. > > Marie-Jose > ----- Original Message ----- > From: "Gorry Fairhurst" > To: > Sent: Thursday, June 10, 2004 6:35 AM > Subject: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt > > > > As WG chair, I request the ipdvb list to consider whether this > > WG is willing to adopt the following individual Internet Draft > > (ID) as a WG ID. > > > > By adopting an individual ID as a working group ID, this WG > > indicates that it intends to be develop this into an RFC, > > according to the WG charter. WG documents should no longer > > be regarded as the property of the individuals who originally > > authored them - the working group as a whole must decide how > > they are shaped, and to see the document to a successful > > conclusion. > > > > If adopted, the Internet Draft will be renamed to start > > with the filename draft-ietf-ipdvb..., and will be listed > > on the IETF web page for this WG. For this document an Editor > > will be appointed to author new text and assist in this process. > > > > --- > > > > A Framework for transmission of IP datagrams over MPEG-2 networks > > Document: draft-fair-ipdvb-req-05.txt > > http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-05.txt > > > > --- > > > > This is being proposed as Charter item No.1. > > http://www.ietf.org/html.charters/ipdvb-charter.html > > > > You are actively encouraged to send email to this WG, > > to help make the decision for adoption. > > Possible recommendations are: > > > > 1) Support for adoption as a working group draft > under our Charter > > i.e. Recommend this Internet Draft to be used as the basis for > > developing an RFC by the ipdvb WG. > > > > 2) Request for non-adoption > > i.e. That there is alternative approaches to > > the problem, and that the current draft is not sufficiently > > developed / or correctly designed ipdvb WG > > > > 3) Out of scope > > i.e. you believe the document to be beyond the scope of the > > approved ipdvb WG charter. > > > > Emails on this topic should be sent to the ipdvb mailing list > > BEFORE 17th June 2004. > > > > > > Gorry Fairhurst > > (ipdvb WG Chair) > > > > > > > > > > From owner-ipdvb@erg.abdn.ac.uk Tue Jun 15 09:20:30 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 i5F8Jihn003200 for ; Tue, 15 Jun 2004 09:19:44 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5F8Ji7C003199 for ipdvb-subscribed-users; Tue, 15 Jun 2004 09:19:44 +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 lin.calsoft.co.in ([203.129.222.68]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5F8II3u003126 for ; Tue, 15 Jun 2004 09:18:20 +0100 (BST) Received: from calsoftwilliam ([203.129.222.92]) by lin.calsoft.co.in (8.11.0/8.11.0) with ESMTP id i5F84wa27122 for ; Tue, 15 Jun 2004 13:34:59 +0530 From: "William StanisLaus" To: Subject: RE: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt Date: Tue, 15 Jun 2004 13:46:35 +0530 Organization: CalSoft Message-ID: <002301c452b1$147a87c0$8c0210ac@calsoftwilliam> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal In-Reply-To: <40C83963.6050504@erg.abdn.ac.uk> X-MailScanner: Found to be clean 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 Count me to support this I-D in WG :) Regards, -William. > -----Original Message----- > From: owner-ipdvb@erg.abdn.ac.uk > [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst > Sent: Thursday, June 10, 2004 4:05 PM > To: ipdvb@erg.abdn.ac.uk > Subject: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt > > > As WG chair, I request the ipdvb list to consider whether this > WG is willing to adopt the following individual Internet Draft > (ID) as a WG ID. > > By adopting an individual ID as a working group ID, this WG > indicates that it intends to be develop this into an RFC, > according to the WG charter. WG documents should no longer > be regarded as the property of the individuals who originally > authored them - the working group as a whole must decide how > they are shaped, and to see the document to a successful > conclusion. > > If adopted, the Internet Draft will be renamed to start > with the filename draft-ietf-ipdvb..., and will be listed > on the IETF web page for this WG. For this document an Editor > will be appointed to author new text and assist in this process. > > --- > > A Framework for transmission of IP datagrams over MPEG-2 networks > Document: draft-fair-ipdvb-req-05.txt > http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-05.txt > > --- > > This is being proposed as Charter item No.1. > http://www.ietf.org/html.charters/ipdvb-charter.html > > You are actively encouraged to send email to this WG, > to help make the decision for adoption. > Possible recommendations are: > > 1) Support for adoption as a working group draft under > our Charter > i.e. Recommend this Internet Draft to be used as the basis for > developing an RFC by the ipdvb WG. > > 2) Request for non-adoption > i.e. That there is alternative approaches to > the problem, and that the current draft is not sufficiently > developed / or correctly designed ipdvb WG > > 3) Out of scope > i.e. you believe the document to be beyond the scope of the > approved ipdvb WG charter. > > Emails on this topic should be sent to the ipdvb mailing list > BEFORE 17th June 2004. > > > Gorry Fairhurst > (ipdvb WG Chair) > > From owner-ipdvb@erg.abdn.ac.uk Tue Jun 15 09:50:32 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 i5F8o3cT004482 for ; Tue, 15 Jun 2004 09:50:03 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5F8o3Fc004479 for ipdvb-subscribed-users; Tue, 15 Jun 2004 09:50:03 +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 cs.tut.fi (root@varis.cs.tut.fi [130.230.4.42]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5F8nEWC004412 for ; Tue, 15 Jun 2004 09:49:14 +0100 (BST) Received: from tut.fi (pc12-95.dmi.tut.fi [130.230.12.95]) by cs.tut.fi (8.12.10/8.12.8) with ESMTP id i5F8nDqA026240 for ; Tue, 15 Jun 2004 11:49:13 +0300 (EET DST) Message-ID: <40CEB7DF.7080703@tut.fi> Date: Tue, 15 Jun 2004 11:48:31 +0300 From: Vinod Kumar MV User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ip-dvb@erg.abdn.ac.uk Subject: Information about ULE References: <200404151924.i3FJOWU05440@ra.udcast.com> <042b01c4232e$686c6ae0$b402a8c0@copernicus> In-Reply-To: <042b01c4232e$686c6ae0$b402a8c0@copernicus> X-Enigmail-Version: 0.83.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; 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 Hello experts, I am a newbie to the subject of DVB over IP. I would be greatful if any of you could direct me to any kind of documentations or tutorial material regarding ULE and its purpose. It would also be great if some body could point out the conceptual difference between ULE and MPE and pros and cons for each of these. best regards Vinod Kumar MV Research Assistant Signal Processing Department Tampere University of Technology Finland From owner-ipdvb@erg.abdn.ac.uk Tue Jun 15 13:55:15 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 i5FCsj7w014165 for ; Tue, 15 Jun 2004 13:54:45 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5FCsjSX014164 for ipdvb-subscribed-users; Tue, 15 Jun 2004 13:54: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 cs.tut.fi (root@varis.cs.tut.fi [130.230.4.42]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5FCs6Yr014115 for ; Tue, 15 Jun 2004 13:54:07 +0100 (BST) Received: from tut.fi (pc12-95.dmi.tut.fi [130.230.12.95]) by cs.tut.fi (8.12.10/8.12.8) with ESMTP id i5FCs7qA007468 for ; Tue, 15 Jun 2004 15:54:07 +0300 (EET DST) Message-ID: <40CEF145.4080704@tut.fi> Date: Tue, 15 Jun 2004 15:53:25 +0300 From: Vinod Kumar MV User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ip-dvb@erg.abdn.ac.uk Subject: Information about IP over DVB !! X-Enigmail-Version: 0.83.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; 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 Hello experts, I am resending this mail because I made a mistake by typing DVB over IP when I actually ment IP over DVB. Sorry for that. I am a newbie to the subject of IP over DVB. I would be greatful if any of you could direct me to any kind of documentations or tutorial material regarding ULE and its purpose. It would also be great if some body could point out the conceptual difference between ULE and MPE and pros and cons for each of these. best regards Vinod Kumar MV Research Assistant Signal Processing Department Tampere University of Technology Finland From owner-ipdvb@erg.abdn.ac.uk Wed Jun 16 21:30:53 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 i5GKTTbb025182 for ; Wed, 16 Jun 2004 21:29:29 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5GKTSO3025181 for ipdvb-subscribed-users; Wed, 16 Jun 2004 21:29:28 +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 mail2.iabg.de (host-62-245-167-132.customer.m-online.net [62.245.167.132]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5GKSPcI025127 for ; Wed, 16 Jun 2004 21:28:25 +0100 (BST) Received: from mail2.iabg.de (localhost [127.0.0.1]) by localhost (Mailserver2 IABG) with ESMTP id 972F71A815 for ; Wed, 16 Jun 2004 22:28:18 +0200 (CEST) Received: from exchange03.iabg.de (exchange03.iabg.de [10.128.200.37]) by mail2.iabg.de (Mailserver2 IABG) with ESMTP id 84A871A6E4 for ; Wed, 16 Jun 2004 22:28:18 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: AW: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt Date: Wed, 16 Jun 2004 22:28:21 +0200 Message-ID: <69A5E767EC979846826F566C7932A3F28CB19F@exchange03.iabg.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt Thread-Index: AcRO3LOLNrAfMIDeT929AU8sDG6SogFA6OLw From: "Fritsche Wolfgang" To: X-ERG-MailScanner: Found to be clean, Found to be clean Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by erg.abdn.ac.uk id i5GKTOKR025176 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 with the necessity of an appropriate requirement document and therefore agree with the adoption as a WG ID. Cheers, Wolfgang > > > As WG chair, I request the ipdvb list to consider whether > this WG is willing to adopt the following individual Internet Draft > (ID) as a WG ID. > > By adopting an individual ID as a working group ID, this WG > indicates that it intends to be develop this into an RFC, > according to the WG charter. WG documents should no longer be > regarded as the property of the individuals who originally > authored them - the working group as a whole must decide how > they are shaped, and to see the document to a successful conclusion. > > If adopted, the Internet Draft will be renamed to start > with the filename draft-ietf-ipdvb..., and will be listed > on the IETF web page for this WG. For this document an Editor > will be appointed to author new text and assist in this process. > > --- > > A Framework for transmission of IP datagrams over MPEG-2 networks > Document: draft-fair-ipdvb-req-05.txt > http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-05.txt > > --- > > This is being proposed as Charter item No.1. > http://www.ietf.org/html.charters/ipdvb-charter.html > > You are actively encouraged to send email to this WG, > to help make the decision for adoption. > Possible recommendations are: > > 1) Support for adoption as a working group draft under > our Charter > i.e. Recommend this Internet Draft to be used as the basis for > developing an RFC by the ipdvb WG. > > 2) Request for non-adoption > i.e. That there is alternative approaches to > the problem, and that the current draft is not sufficiently > developed / or correctly designed ipdvb WG > > 3) Out of scope > i.e. you believe the document to be beyond the scope of the > approved ipdvb WG charter. > > Emails on this topic should be sent to the ipdvb mailing list > BEFORE 17th June 2004. > > > Gorry Fairhurst > (ipdvb WG Chair) > > > From owner-ipdvb@erg.abdn.ac.uk Sat Jun 19 08:07:13 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 i5J746Wu000333 for ; Sat, 19 Jun 2004 08:04:06 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5J745ge000332 for ipdvb-subscribed-users; Sat, 19 Jun 2004 08:04:05 +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.64] (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 i5J72fpp000259 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Sat, 19 Jun 2004 08:02:43 +0100 (BST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Sat, 19 Jun 2004 08:03:19 +0100 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 Subject: Ipdvb: progression of draft-fair-ipdvb-req-05.txt to WG draft 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 am pleased to announce the adoption of the following draft as a Working Group work item. This draft will be re-issued as a working group draft intended for publication as an INFORMATIONAL RFC. Title : Requirements for transmission of IP datagrams over MPEG-2 networks Author(s) : G. Fairhurst, et al. Filename : draft-fair-ipdvb-req-05.txt Pages : 38 Date : 2004-6-8 Marie-Jose Montpetit made a significant contribution to the last revision of this draft - including much help with bringing this document into a better shape. I am therefore pleased to announce that she will be added as an author, and will also as the document Editor on behalf of the working group. Please do send any known issues, or suggestions for improvement to the list for her attention. Gorry Fairhurst Ipdvb WG chair From owner-ipdvb@erg.abdn.ac.uk Mon Jun 21 07:14:49 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 i5L6EEFs000092 for ; Mon, 21 Jun 2004 07:14:14 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5L6EE3O000091 for ipdvb-subscribed-users; Mon, 21 Jun 2004 07:14:14 +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 mail2.iabg.de (host-62-245-167-132.customer.m-online.net [62.245.167.132]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5L6DYhf000050 for ; Mon, 21 Jun 2004 07:13:34 +0100 (BST) Received: from mail2.iabg.de (localhost [127.0.0.1]) by localhost (Mailserver2 IABG) with ESMTP id 4EF601D42A for ; Mon, 21 Jun 2004 08:13:28 +0200 (CEST) Received: from exchange03.iabg.de (exchange03.iabg.de [10.128.200.37]) by mail2.iabg.de (Mailserver2 IABG) with ESMTP id 3DB581A7A2 for ; Mon, 21 Jun 2004 08:13:28 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt Date: Mon, 21 Jun 2004 08:13:29 +0200 Message-ID: <69A5E767EC979846826F566C7932A3F28E0AB2@exchange03.iabg.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt Thread-Index: AcRO3LOLNrAfMIDeT929AU8sDG6SogIeheIA From: "Gessler Gerhard" To: X-ERG-MailScanner: Found to be clean, Found to be clean Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by erg.abdn.ac.uk id i5L6ECoc000088 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 support the adoption of draft-fair-ipdvb-req-05.txt as WG ID. Regards, Gerhard -------------------------------------------- Gerhard Gessler Communication Networks, IABG mbH Einsteinstr. 20 85521 Ottobrunn, Germany Telefon: +49 89 6088 - 2021 Fax: +49 89 6088 - 2845 E-Mail: gessler@iabg.de > -----Original Message----- > From: owner-ipdvb@erg.abdn.ac.uk > [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Gorry Fairhurst > Sent: Thursday, June 10, 2004 12:35 PM > To: ipdvb@erg.abdn.ac.uk > Subject: Call for the ipdvb WG to adopt: draft-fair-ipdvb-req-05.txt > > > As WG chair, I request the ipdvb list to consider whether > this WG is willing to adopt the following individual Internet Draft > (ID) as a WG ID. > > By adopting an individual ID as a working group ID, this WG > indicates that it intends to be develop this into an RFC, > according to the WG charter. WG documents should no longer > be regarded as the property of the individuals who > originally authored them - the working group as a whole > must decide how they are shaped, and to see the document to > a successful conclusion. > > If adopted, the Internet Draft will be renamed to start > with the filename draft-ietf-ipdvb..., and will be listed > on the IETF web page for this WG. For this document an > Editor will be appointed to author new text and assist in > this process. > > --- > > A Framework for transmission of IP datagrams over MPEG-2 networks > Document: draft-fair-ipdvb-req-05.txt > http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-05.txt > > --- > > This is being proposed as Charter item No.1. > http://www.ietf.org/html.charters/ipdvb-charter.html > > You are actively encouraged to send email to this WG, > to help make the decision for adoption. > Possible recommendations are: > > 1) Support for adoption as a working group draft > under our Charter > i.e. Recommend this Internet Draft to be used as the basis for > developing an RFC by the ipdvb WG. > > 2) Request for non-adoption > i.e. That there is alternative approaches to > the problem, and that the current draft is not sufficiently > developed / or correctly designed ipdvb WG > > 3) Out of scope > i.e. you believe the document to be beyond the scope of the > approved ipdvb WG charter. > > Emails on this topic should be sent to the ipdvb mailing > list BEFORE 17th June 2004. > > > Gorry Fairhurst > (ipdvb WG Chair) > > > From owner-ipdvb@erg.abdn.ac.uk Mon Jun 21 14:11:37 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 i5LDB191015034 for ; Mon, 21 Jun 2004 14:11:01 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5LDB1QF015033 for ipdvb-subscribed-users; Mon, 21 Jun 2004 14:11:01 +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 osiris.femmecomp.com (IDENT:Ju73palSUbnurxedD+X7sW7AbBIJUYnx@osiris.femmecomp.com [63.103.85.38]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5LDATH4015003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 21 Jun 2004 14:10:31 +0100 (BST) Received: from gkinal (anubis.femmecomp.com [63.103.85.2]) by osiris.femmecomp.com (8.12.8/8.12.8) with ESMTP id i5LDBMDN006397 for ; Mon, 21 Jun 2004 09:11:22 -0400 From: "George Kinal" To: ipdvb@erg.abdn.ac.uk Date: Mon, 21 Jun 2004 09:10:28 -0400 MIME-Version: 1.0 Subject: unsubscribe Message-ID: <40D6A604.32577.EF839@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body 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 Changing jobs. Unsubscribe this address please. George Kinal From owner-ipdvb@erg.abdn.ac.uk Tue Jun 22 10:26:39 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 i5M9PQ4t026125 for ; Tue, 22 Jun 2004 10:25:26 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5M9PQXs026124 for ipdvb-subscribed-users; Tue, 22 Jun 2004 10:25:26 +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-ipv6.erg.abdn.ac.uk [IPv6:2001:630:241:1:20a:95ff:fe7d:5f0c]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5M9OOoh026070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 22 Jun 2004 10:24:24 +0100 (BST) Message-ID: <40D7FAC8.6000207@erg.abdn.ac.uk> Date: Tue, 22 Jun 2004 10:24:24 +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: IETF 60 - Meeting Slot confirmed for ipdvb WG 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 Please note that the Sixtieth IETF is scheduled for August 1 - 6, 2004, in San Diego, meeting information and the registration procedure is provided at: http://www.ietf.org/meetings/IETF-60.html We have been allocated a 2 hour meeting, and an Agenda will be posted nearer the time. Before this meeting I would like to see the following resolved on the list: (i) Discussion on all pending issues regarding ULE to enable progression to Working Group Last Call. (ii) Decision on whether to accept/modify/reject the XULE proposal. (iii) Progression of the architecture document (previously draft-fair-ipdvb-req-05.txt) towards completion. (iv) Any other inputs/ideas related to our Charter. A draft Agenda is now available at: http://www.ietf.org/meetings/agenda_60.txt - Although newcomers should note that the dates and timing on this Agenda may still change as the schedule of working groups is adjusted to include BoFs and to reduce overlap between meetings that rely on the same people. This will be the first official IETF WG meeting, and I look forward to a successful meeting and to meeting some of you for the first time! Best wishes, Gorry Fairhurst (ipdvb WG Chair) From owner-ipdvb@erg.abdn.ac.uk Wed Jun 23 13:52:33 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 i5NCphQB024632 for ; Wed, 23 Jun 2004 13:51:43 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5NCpgLG024631 for ipdvb-subscribed-users; Wed, 23 Jun 2004 13:51:42 +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 enterprise (enterprise-mac.erg.abdn.ac.uk [139.133.207.102]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5NCogvn024582 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 23 Jun 2004 13:50:42 +0100 (BST) From: "Michael Forrest" To: Subject: IPDVB List Archive Date: Wed, 23 Jun 2004 13:50:19 +0100 Organization: Electronics Research Group, Dept of Engineering, University of Aberdeen Message-ID: <001501c45920$a409d5b0$66cf858b@enterprise> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal X-ERG-MailScanner: Found to be clean, Found to be clean Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by erg.abdn.ac.uk id i5NCpeH7024628 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 have started to archive the email at the IETF archive server, at: ftp://ftp.ietf.org/ietf-mail-archive/ipdvb/ We hope that this arhive will soon be fixed and will duplicate the web-based archive already run by the ipdvb working group. Thanks, Michael (ipdvb admin) -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ --------------------------------------------- From owner-ipdvb@erg.abdn.ac.uk Wed Jun 23 14:14:42 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 i5NDE5bK025540 for ; Wed, 23 Jun 2004 14:14:05 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5NDE4Nd025539 for ipdvb-subscribed-users; Wed, 23 Jun 2004 14:14:05 +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 i5NDDPKU025495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 23 Jun 2004 14:13:27 +0100 (BST) Received: from ([199.29.3.1]) by maildc2.nab.org with ESMTP ; Wed, 23 Jun 2004 09:12:46 -0400 Received: by mail.NAB.ORG with Internet Mail Service (5.5.2653.19) id ; Wed, 23 Jun 2004 09:12:46 -0400 Message-ID: <5A659834E1607E4EBD72FCE2FE5C9CF102FEC35D@mail.NAB.ORG> From: "Allison, Art" To: "'ipdvb@erg.abdn.ac.uk'" Cc: "'michael@erg.abdn.ac.uk'" Subject: RE: IPDVB List Archive Date: Wed, 23 Jun 2004 09:12:46 -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 If you can prevent 'bot scan/mining of email addresses from the new repository that would be a great service to the community. Art ::{)> Art Allison Director Advanced Engineering NAB 1771 N St NW Washington DC 20036 202 429 5418 -----Original Message----- From: Michael Forrest [mailto:michael@erg.abdn.ac.uk] Sent: Wednesday, June 23, 2004 8:50 AM To: ipdvb@erg.abdn.ac.uk Subject: IPDVB List Archive We have started to archive the email at the IETF archive server, at: ftp://ftp.ietf.org/ietf-mail-archive/ipdvb/ We hope that this arhive will soon be fixed and will duplicate the web-based archive already run by the ipdvb working group. Thanks, Michael (ipdvb admin) -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ --------------------------------------------- -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ --------------------------------------------- From owner-ipdvb@erg.abdn.ac.uk Thu Jun 24 09:08:52 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 i5O88LMO005498 for ; Thu, 24 Jun 2004 09:08:21 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5O88Kk5005497 for ipdvb-subscribed-users; Thu, 24 Jun 2004 09:08:20 +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-ipv6.erg.abdn.ac.uk [IPv6:2001:630:241:1:20a:95ff:fe7d:5f0c]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5O87gIm005458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 24 Jun 2004 09:07:42 +0100 (BST) Message-ID: <40DA8BCE.9090607@erg.abdn.ac.uk> Date: Thu, 24 Jun 2004 09:07:42 +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: IPDVB List Archive References: <5A659834E1607E4EBD72FCE2FE5C9CF102FEC35D@mail.NAB.ORG> In-Reply-To: <5A659834E1607E4EBD72FCE2FE5C9CF102FEC35D@mail.NAB.ORG> 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 Good point. This second copy of the list will be maintained by the IETF as a record of the work in each of their groups. Scanning/harvesting of internet sites by "bots" is an annoying fact of life, so this could be a good suggestion - but one that would have to be implemented as a policy decision by the IETF for all archives, and there are practical difficulties doing this on this sort of scale. Discussions on this sort of topic can take place on the IETF general mailing list. best wishes, Gorry (ipdvb WG Chair) Allison, Art wrote: > If you can prevent 'bot scan/mining of email addresses from the new > repository that would be a great service to the community. > > Art > ::{)> > Art Allison > Director Advanced Engineering > NAB > 1771 N St NW > Washington DC 20036 > 202 429 5418 > > > -----Original Message----- > From: Michael Forrest [mailto:michael@erg.abdn.ac.uk] > Sent: Wednesday, June 23, 2004 8:50 AM > To: ipdvb@erg.abdn.ac.uk > Subject: IPDVB List Archive > > > > We have started to archive the email at the IETF archive server, at: > > ftp://ftp.ietf.org/ietf-mail-archive/ipdvb/ > > We hope that this arhive will soon be fixed and will duplicate the web-based > archive already run by the ipdvb working group. > > Thanks, > > Michael (ipdvb admin) > > > -------------- ipdvb list ------------------- > To unsubscribe from the ipdvb list :- > Email majordomo@erg.abdn.ac.uk with the words > unsubscribe ipdvb > in the body of the message. > http://www.erg.abdn.ac.uk/ipdvb/ > --------------------------------------------- > -------------- ipdvb list ------------------- > To unsubscribe from the ipdvb list :- > Email majordomo@erg.abdn.ac.uk with the words > unsubscribe ipdvb > in the body of the message. > http://www.erg.abdn.ac.uk/ipdvb/ > --------------------------------------------- > > -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ --------------------------------------------- From owner-ipdvb@erg.abdn.ac.uk Thu Jun 24 14:14:24 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 i5ODDes3017248 for ; Thu, 24 Jun 2004 14:13:40 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5ODDe57017242 for ipdvb-subscribed-users; Thu, 24 Jun 2004 14:13: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 esacom57-int.estec.esa.int (esacom57-ext.estec.esa.int [131.176.107.4]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5ODCaDb017184 for ; Thu, 24 Jun 2004 14:12:36 +0100 (BST) Received: from esacom52.estec.esa.int (esacom52.estec.esa.int [131.176.7.7]) by esacom57-int.estec.esa.int (8.12.10/8.12.10/ESA-External-v3.2) with ESMTP id i5ODCVWP018834 for ; Thu, 24 Jun 2004 15:12:31 +0200 (MET DST) Received: from estecmta1.estec.esa.int (estecmta1.estec.esa.int [131.176.1.131]) by esacom52.estec.esa.int (8.12.10/8.12.10/ESA-Internal-v3.2) with ESMTP id i5ODCU5L017101 for ; Thu, 24 Jun 2004 15:12:30 +0200 (MET DST) Subject: ESA project deliverables of ip-over-dvb/ULE projects available To: ipdvb@erg.abdn.ac.uk X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: Frank.Zeppenfeldt@esa.int Date: Thu, 24 Jun 2004 14:12:28 +0100 X-MIMETrack: Serialize by Router on estecmta1/estec/ESA(Release 5.0.11 |July 24, 2002) at 24/06/2004 03:12:30 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii 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 would like to inform the list that during the last months, two projects funded by ESA (European Space Agency) have been finalised in the area of IP over DVB encapsulations and that the main deliverables are available via our website. The first project was carried out by a group under the leadership of Joanneum Research (Austria) and its deliverables can be found on: http://telecom.esa.int/telecom/www/object/index.cfm?fobjectid=13503 The second project was lead by IABG (Germany) and has its deliverables on: http://telecom.esa.int/telecom/www/object/index.cfm?fobjectid=11271 Check the Documentation banner at the right hand side. (ESA policy is that a password needs to be requested for some reports, but this a mere formality). In addition, on the IABG webpage the results of ULE interoperability tests between various sender and receiver equipment are available. More details on software, equipment and documents is available from the contact persons listed on the webpages from both projects. Encapsulator equipment and ULE/DVB-S drivers for Linux from the first project, in particular from GCS/University of Salzburg, are now being installed by another ESA project dealing with IPv6 over Satellite in general, to provide native IPv6 over ULE/MPEG-2/DVB-S for a few months to a number of research networks in Central Asian countries. Regards, Frank -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ --------------------------------------------- From owner-ipdvb@erg.abdn.ac.uk Mon Jun 28 08:29:16 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 i5S7SQle004848 for ; Mon, 28 Jun 2004 08:28:26 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5S7SQcg004847 for ipdvb-subscribed-users; Mon, 28 Jun 2004 08:28:26 +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 loewe.cosy.sbg.ac.at (loewe.cosy.sbg.ac.at [141.201.2.12]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5S7RdKx004800 for ; Mon, 28 Jun 2004 08:27:39 +0100 (BST) Received: from [141.201.123.101] (kaenguruh.cosy.sbg.ac.at [141.201.123.101]) by loewe.cosy.sbg.ac.at (8.8.8/8.8.7) with ESMTP id JAA11947 for ; Mon, 28 Jun 2004 09:27:38 +0200 (MET DST) Message-ID: <40DFC86A.2060000@cosy.sbg.ac.at> Date: Mon, 28 Jun 2004 09:27:38 +0200 From: Hilmar Linder Organization: Universitaet Salzburg, Fachbereich Scientific Computing User-Agent: Mozilla Thunderbird 0.6 (X11/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ip-dvb@erg.abdn.ac.uk Subject: ULE Extension Header Thoughts 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 when thinking about the extension headers for ULE we left several questions untouched in the first draft. Therefore, I would like the list to comment on the following items: o) Should we define the chaining mechanism: All mandatory extension headers MUST/SHOULD be inserted by the encapsulator prior to any extension headers in order to optimize receiver processing. A receiver is such able to discard a SNDU whose mandatory extension header is not supported or is to be rejected without having to investigate and eventually process optional extension headers beforehand. o) Does it make sense to define the header types 0x002 and 0x003 as mandatory encryption header (section 2.1). As different encryptions require different extension headers we should probably only define that the next-layer-header types should be larger than 0x001 and smaller than 0x0100. o) How many different encryption schemes do we expect to support with the ULE extension headers? Is the type range allocated suffciently large? o) Will we see different odd/even encryption header types for IPv4 and IPv6 traffic? Any other thoughts? -Hilmar Linder (co-editor) -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ --------------------------------------------- From owner-ipdvb@erg.abdn.ac.uk Tue Jun 29 16:30:46 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 i5TFTBkB014233 for ; Tue, 29 Jun 2004 16:29:11 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5TFTAJE014231 for ipdvb-subscribed-users; Tue, 29 Jun 2004 16:29:11 +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 lin.calsoft.co.in ([203.129.222.68]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5TFRv7N014154 for ; Tue, 29 Jun 2004 16:28:03 +0100 (BST) Received: from calsoftwilliam ([203.129.222.92]) by lin.calsoft.co.in (8.11.0/8.11.0) with ESMTP id i5TFDOa31411 for ; Tue, 29 Jun 2004 20:43:25 +0530 From: "William StanisLaus" To: Subject: RE: ULE Extension Header Thoughts Date: Tue, 29 Jun 2004 20:56:05 +0530 Organization: CalSoft Message-ID: <00bf01c45ded$66605c80$8c0210ac@calsoftwilliam> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <40DFC86A.2060000@cosy.sbg.ac.at> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal X-MailScanner: Found to be clean 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 Please see my response inlined... > -----Original Message----- > From: owner-ipdvb@erg.abdn.ac.uk > [mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Hilmar Linder > Sent: Monday, June 28, 2004 12:58 PM > To: ip-dvb@erg.abdn.ac.uk > Subject: ULE Extension Header Thoughts > > > when thinking about the extension headers for ULE we left several > questions untouched in the first draft. Therefore, I would > like the list > to comment on the following items: > > o) Should we define the chaining mechanism: All mandatory extension > headers MUST/SHOULD be inserted by the encapsulator prior to any > extension headers in order to optimize receiver processing. A > receiver > is such able to discard a SNDU whose mandatory extension > header is not > supported or is to be rejected without having to investigate and > eventually process optional extension headers beforehand. William> It MUST be implemented all mandatory headers before any optional headers and actual data. Since at any cost if mandatory header is not supported/implemented the receiver MUST drop the SNDU. Inserting optional header before mandatory headers will give room to unnecessary processing. > o) Does it make sense to define the header types 0x002 and 0x003 as > mandatory encryption header (section 2.1). As different encryptions > require different extension headers we should probably only > define that > the next-layer-header types should be larger than 0x001 and > smaller than > 0x0100. William> Needs clarification, encryption header is a more generic term, what type of encryption MUST be defined with the type field. Can be more than one encryption technique used. But i wonder, no point in using predefined encryption technique without key exchange. Hope this is the next level of discussion. How and What type of encryption we are going to support > o) How many different encryption schemes do we expect to support with > the ULE extension headers? Is the type range allocated > suffciently large? William> Should be suffciently large. > o) Will we see different odd/even encryption header types for > IPv4 and > IPv6 traffic? William> the encryption we are discussing here is L2 encryption and nothing to do with the IPv4 and IPv6 i believe, Since there are well defined encryptions already available for L3 i.e. IPSEC. > > Any other thoughts? > William> my personnel opinion on extension header is just to give room to support future extensions, and we should keep as minimal as possible ULE for better performance and bring down the overhead of exhastive conditional checks. > -Hilmar Linder > (co-editor) > Best Regards, William. > > -------------- ipdvb list ------------------- > To unsubscribe from the ipdvb list :- > Email majordomo@erg.abdn.ac.uk with the words > unsubscribe ipdvb > in the body of the message. > http://www.erg.abdn.ac.uk/ipdvb/ > --------------------------------------------- > -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ --------------------------------------------- From owner-ipdvb@erg.abdn.ac.uk Tue Jun 29 19:30:57 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 i5TIUGIN021486 for ; Tue, 29 Jun 2004 19:30:16 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5TIUGPe021485 for ipdvb-subscribed-users; Tue, 29 Jun 2004 19:30: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 out011.verizon.net (out011pub.verizon.net [206.46.170.135]) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5TIT7qe021413 for ; Tue, 29 Jun 2004 19:29:08 +0100 (BST) Received: from copernicus ([68.163.134.93]) by out011.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040629182906.FHIV18566.out011.verizon.net@copernicus> for ; Tue, 29 Jun 2004 13:29:06 -0500 Message-ID: <016e01c45e06$f8df1240$b402a8c0@copernicus> From: "Marie-Jose Montpetit" To: Subject: IPDVB Framework ID Date: Tue, 29 Jun 2004 14:29:04 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0169_01C45DE5.6DE42A20" 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 out011.verizon.net from [68.163.134.93] at Tue, 29 Jun 2004 13:29:03 -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_0169_01C45DE5.6DE42A20 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable List: I'd like to get final comments on: A Framework for transmission of IP datagrams over MPEG-2 networks Document: draft-fair-ipdvb-req-05.txt http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-05.txt by Thursday 1st of July. I will fix the document with the comment I have and any potential new = one and submit by Friday. Thanks! Marie-Jose Montpetit ------=_NextPart_000_0169_01C45DE5.6DE42A20 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
List:
 
I'd like to get final comments = on:
 
A Framework for transmission of IP = datagrams over=20 MPEG-2 networks
Document: draft-fair-ipdvb-req-05.txt
= http://www.ietf.org/internet-drafts/draft-fair-ipdvb-req-05.txt<= /FONT>
by Thursday 1st of=20 July.
 
I will fix the document with the=20 comment I have and any potential new one and submit by = Friday.
 
Thanks!
 
Marie-Jose = Montpetit
------=_NextPart_000_0169_01C45DE5.6DE42A20-- -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ --------------------------------------------- From owner-ipdvb@erg.abdn.ac.uk Wed Jun 30 09:30:25 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 i5U8TfiT020937 for ; Wed, 30 Jun 2004 09:29:41 +0100 (BST) Received: (from majordomo.lists@localhost) by mavis.erg.abdn.ac.uk (8.12.11/8.12.2/Submit) id i5U8TevY020936 for ipdvb-subscribed-users; Wed, 30 Jun 2004 09:29: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 erg.abdn.ac.uk (gresley-ipv6.erg.abdn.ac.uk [IPv6:2001:630:241:1:20a:95ff:fe7d:5f0c]) (authenticated bits=0) by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id i5U8StZH020883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 30 Jun 2004 09:28:56 +0100 (BST) Message-ID: <40E279C8.2070407@erg.abdn.ac.uk> Date: Wed, 30 Jun 2004 09:28:56 +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: ULE Extension Header Thoughts - Mandatory extensions References: <00bf01c45ded$66605c80$8c0210ac@calsoftwilliam> In-Reply-To: <00bf01c45ded$66605c80$8c0210ac@calsoftwilliam> 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 Hilmar, William, other people on the list, can I make some comments as a WG Chair and solict feedbacok from the list: I'm first trying to work out if there are potential issues when the ordering of Mandatory Extension headers could result in reduced inter-operability (i.e. Where a receiver will fail/behave unexpectedly because of the ordering). William StanisLaus wrote: > Please see my response inlined... > > >>-----Original Message----- >>From: owner-ipdvb@erg.abdn.ac.uk >>[mailto:owner-ipdvb@erg.abdn.ac.uk] On Behalf Of Hilmar Linder >>Sent: Monday, June 28, 2004 12:58 PM >>To: ip-dvb@erg.abdn.ac.uk >>Subject: ULE Extension Header Thoughts >> >> >>when thinking about the extension headers for ULE we left several >>questions untouched in the first draft. Therefore, I would >>like the list >>to comment on the following items: >> >>o) Should we define the chaining mechanism: All mandatory extension >>headers MUST/SHOULD be inserted by the encapsulator prior to any >>extension headers in order to optimize receiver processing. A >>receiver >>is such able to discard a SNDU whose mandatory extension >>header is not >>supported or is to be rejected without having to investigate and >>eventually process optional extension headers beforehand. > Agreed, if an operator chose to do this it could be a waste of processing resources to process extension headers belonging to a PDU, and then ultimately discard that PDU. If the first extension was always present in all SNDUs however, teh cost of processing could be reduced by pattern-matching the headers (as in TCP header prediction), so the cost need not always be as much as it seems. > > William> It MUST be implemented all mandatory headers before any > optional headers and actual data. Since at any cost if mandatory header > is not supported/implemented the receiver MUST drop the SNDU. Inserting > optional header before mandatory headers will give room to unnecessary > processing. > > Normally when the IETF mandates MUST be implemented, it implies an interoperability issue. A good ethos is for receivers to liberal in what they receive (that way we avoid painful discoveries when new uses appear). * I wonder though if this is really an inter-working issue, or purely an optimisation that a gateway could use, in the same way the NPA address can be used as a pre-filter or not, depending on topology, bandwidth cost, etc. In other words, what breaks if we allow arbitrary ordering? * Another issue is what we could we loose by requiring specific ordering? If there are potential issues where this results in reduced inter-operability (i.e. Where a receiver will fail because of the ordering) then I think we should specify - If there are only performance-related issues then we could identify these, but I'd urge being liberal in what the Receiver should accept - implementers/operators can still optimise Receivers for the most common code-path. Gorry ipdvb WG Chair -------------- ipdvb list ------------------- To unsubscribe from the ipdvb list :- Email majordomo@erg.abdn.ac.uk with the words unsubscribe ipdvb in the body of the message. http://www.erg.abdn.ac.uk/ipdvb/ ---------------------------------------------