From owner-ipdvb@erg.abdn.ac.uk Fri Oct 17 00:23:43 2008 Return-Path: X-Original-To: ietfarch-ipdvb-archive@core3.amsl.com Delivered-To: ietfarch-ipdvb-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB2D23A680C for ; Fri, 17 Oct 2008 00:23:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.137 X-Spam-Level: X-Spam-Status: No, score=-0.137 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, MIME_8BIT_HEADER=0.3, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WKlMjCMNCpg for ; Fri, 17 Oct 2008 00:23:43 -0700 (PDT) Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 71E293A63CB for ; Fri, 17 Oct 2008 00:23:41 -0700 (PDT) Received: from dee.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id m9H75E79013502 for ; Fri, 17 Oct 2008 08:05:14 +0100 (BST) Received: (from majordomo.lists@localhost) by dee.erg.abdn.ac.uk (8.13.4/8.12.2/Submit) id m9H75Eba013501 for ipdvb-subscribed-users; Fri, 17 Oct 2008 08:05:14 +0100 (BST) X-Authentication-Warning: dee.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from nav6.org ([219.93.2.80]) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id m9H74nNT013469 for ; Fri, 17 Oct 2008 08:04:51 +0100 (BST) Received: from localhost (unknown [127.0.0.1]) by nav6.org (Postfix) with ESMTP id EEB6D1D6017C; Fri, 17 Oct 2008 07:39:44 +0000 (UTC) X-Virus-Scanned: amavisd-new at nav6.org Received: from [202.249.25.156] (unknown [202.249.25.156]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by nav6.org (Postfix) with ESMTP id 5DB331D60170; Fri, 17 Oct 2008 15:39:30 +0800 (MYT) Message-ID: <48F838A1.5000406@nav6.org> Date: Fri, 17 Oct 2008 16:02:57 +0900 From: =?UTF-8?B?IkFuZyBXYXkgQ2h1YW5nIDzmtKrkvJ/lo64+Ig==?= User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: "ipdvb@erg.abdn.ac.uk" CC: TC Wan Subject: New I-D has been submitted for draft-wan-ipdvb-rohc Content-Type: text/plain; charset=UTF-8; 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 Hi all, I've just submitted the latest draft to IETF. The URL: https://datatracker.ietf.org/idst/status.cgi?submission_id=9771 The following is a summary of changes that went into this draft: - Introduce a field called RefID (reference ID) in RCPNP message that used to ack/nack another message with the same ID. - Reorganize the content so all causes of negative acknowledgement are now put under Negative acknowlegement section. - Introduce heartbeat message in RCPNP that will be sent periodically when ROHC channel is idle. This is used to detect cases where compressor/decompressor terminates abnormally. - In the section where interaction of RCPNP is shown, how RefID and ID are used was added. In addition, a case where abnormal termination is also shown. Any comment on the latest draft? In addition, we would like to discuss and possibly include the following ideas for the next revision: 1. Network with only 2 nodes may avoid the steps involve in the learning of network topology. Broadcast/multicast traffic can be compressed in this case. My guess is that this can achieved by gateway machine by detecting how many receiver frontend. If there is only one receiver frontend, then it is safe to assume the network only consists of 2 nodes. Our definition of node is limited to receive capable feed. Of course, I am likely to be wrong. 2. How to enable compression of broadcast/multicast traffic if the network has more than 2 nodes? One idea is to have compressor gateway send a beacon signal about parameters of ROHC channel for broadcast/multicast traffic through uncompressed channel periodically There are several challenges that must be handled for this case. - Firstly, if one of the receiver gateway can't accept the ROHC channel parameter (e.g doesn't support certain profile or doesn't ROHC decompression), then compression of broadcast/multicast can't proceed. - There may be cases where receiver gateway joins the network after compressor gateway has started transmission of compressed packet. In this situation, the receiver gateway won't be able to decompress the packet until it receives the beacon and until the compressor's context falls back to IR state. Thus, context of compressor must periodically fall back to IR state after certain time (this may consumes more bandwidth than having uncompressed packet for certain cases depending on how frequent it falls back to IR state). 3. Only decompressor gateway can initiate the negotiation of ROHC channel in current draft. I think it is sufficient, so is there a need to specify a way to let compressor gateway to initiate the negotiation of ROHC channel? Anyway, I had a quick glance at the drafts related to security extension mentioned in the last IETF meeting, but I have no idea how it can be used to overcome the problem of address spoofing vulnerability mentioned in our draft. Thanks for reading this lengthy email. Regards, Ang Way Chuang From owner-ipdvb@erg.abdn.ac.uk Mon Oct 27 07:33:28 2008 Return-Path: X-Original-To: ietfarch-ipdvb-archive@core3.amsl.com Delivered-To: ietfarch-ipdvb-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6F813A6B47 for ; Mon, 27 Oct 2008 07:33:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70vv-uApRo+Y for ; Mon, 27 Oct 2008 07:33:28 -0700 (PDT) Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id B63AC3A6B61 for ; Mon, 27 Oct 2008 07:33:26 -0700 (PDT) Received: from dee.erg.abdn.ac.uk (localhost [IPv6:::1]) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id m9RECkNF005934 for ; Mon, 27 Oct 2008 14:12:46 GMT Received: (from majordomo.lists@localhost) by dee.erg.abdn.ac.uk (8.13.4/8.12.2/Submit) id m9RECkLY005933 for ipdvb-subscribed-users; Mon, 27 Oct 2008 14:12:46 GMT X-Authentication-Warning: dee.erg.abdn.ac.uk: majordomo.lists set sender to owner-ipdvb@erg.abdn.ac.uk using -f Received: from Gorry-Fairhursts-Laptop.local (fgrpf.plus.com [212.159.18.54]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id m9RECV2p005911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Mon, 27 Oct 2008 14:12:31 GMT Message-ID: <4905CC4F.2030807@erg.abdn.ac.uk> Date: Mon, 27 Oct 2008 14:12:31 +0000 From: Gorry Fairhurst Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683. User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: ipdvb@erg.abdn.ac.uk Subject: IPDVB Working Group Status for IETF-73 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 Dear all The current IPDVB status is at: http://tools.ietf.org/wg/ipdvb/ The following drafts have now been sent to our AD, with a request for publication: draft-ietf-ipdvb-sec-req-09 WG: 2008-08-23 draft-combes-ipdvb-mib-rcs-04 AD-Sponsored Submission. Please let me know if you have any items you feel should be discussed, or brought to AD's attention at the next IETF meeting. Currently, no official meeting has been scheduled, since there are no WG work items within the group - However, there ARE individual submissions that are progressing (see page). Even if no official meeting is scheduled, there will be plenty of opportunity for discussion either face-to-face or via email. Please let me know if you have issues or topics you'd like to discuss. Best wishes, Gorry Fairhurst