IETF Logo Mail Archive

Re: [Megaco] H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt

<bruno.chatras@orange.com> Fri, 02 December 2011 10:27 UTC

Return-Path: <bruno.chatras@orange.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 106DA21F9938 for <megaco@ietfa.amsl.com>; Fri, 2 Dec 2011 02:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aF+G8VUHp+PH for <megaco@ietfa.amsl.com>; Fri, 2 Dec 2011 02:27:32 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id 388F221F9377 for <megaco@ietf.org>; Fri, 2 Dec 2011 02:27:32 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 02F0C8B8004; Fri, 2 Dec 2011 11:28:36 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id ED9038B8001; Fri, 2 Dec 2011 11:28:35 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Fri, 2 Dec 2011 11:27:29 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 02 Dec 2011 11:27:28 +0100
Message-ID: <9ECCF01B52E7AB408A7EB85352642141038D4128@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <5F7BCCF5541B7444830A2288ABBEBC9621619009A9@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Megaco] H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt
Thread-Index: Acyw0b1mZgB+i5MASuuh3y0fTiEWmQABaSFgAAEimXA=
References: <5F7BCCF5541B7444830A2288ABBEBC9621619009A9@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
From: bruno.chatras@orange.com
To: albrecht.schwarz@alcatel-lucent.com
X-OriginalArrivalTime: 02 Dec 2011 10:27:29.0778 (UTC) FILETIME=[FE9B3520:01CCB0DC]
Cc: megaco@ietf.org
Subject: Re: [Megaco] H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 10:27:33 -0000

Yes indeed it would be useful to draft something about H.248 vs. OF/ForCES

BTW, reading H.248.64 once more, a new question stroked me! H.248.64 specifies that an incoming packet whose DA does not match the local space is forwarded to an IPR context. I believe that there are cases where the B2BIH mode can be used although the DA does not match the local space. The configuration I have in mind is one where the MGC creates a context with two terminations and set explicitly the LD and RD on both sides (i.e. no wildcard).

BC

> -----Message d'origine-----
> De : megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] De la
> part de Schwarz, Albrecht (Albrecht)
> Envoyé : vendredi 2 décembre 2011 10:50
> À : CHATRAS Bruno RD-CORE-ISS
> Cc : megaco@ietf.org
> Objet : [Megaco] H.248.64 vs ForCES vs OpenFlow; FW: I-D Action: draft-
> wang-forces-compare-openflow-forces-00.txt
> 
> Bruno, fyi, a first analysis appears, comparison could be extended for
> H.248.64 ...
> 
> 
> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-
> bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Freitag, 2. Dezember 2011 10:07
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-wang-forces-compare-openflow-forces-00.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 	Title           : Analysis of Comparisons between OpenFlow and
> ForCES
> 	Author(s)       : Zhiliang Wang
>                           Tina Tsou
>                           Jing Huang
>                           Xingang Shi
>                           Xia Yin
> 	Filename        : draft-wang-forces-compare-openflow-forces-
> 00.txt
> 	Pages           : 12
> 	Date            : 2011-12-02
> 
>    While both ForCES and OpenFlow follow the basic idea of separations
>    of forwarding plane and control plane in network elements, they are
>    technically very different. This document analyzes the differences
>    between OpenFlow and ForCES technically from the aspects of goals,
>    architecture, forwarding model and protocol interface. The two
>    techniques can learn much from each other in their standardization
>    process.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-wang-forces-compare-openflow-
> forces-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-wang-forces-compare-openflow-
> forces-00.txt
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco

v2.23.0 | Report a Bug | By Email