IETF Logo Mail Archive

Re: [multrans] link to meeting slides for multrans BoF

Simon Perreault <simon.perreault@viagenie.ca> Sat, 12 November 2011 14:52 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: multrans@ietfa.amsl.com
Delivered-To: multrans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38F7221F8922 for <multrans@ietfa.amsl.com>; Sat, 12 Nov 2011 06:52:47 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95iYCD7HudtV for <multrans@ietfa.amsl.com>; Sat, 12 Nov 2011 06:52:46 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id 76F8021F8906 for <multrans@ietf.org>; Sat, 12 Nov 2011 06:52:46 -0800 (PST)
Received: from banana.viagenie.ca (210.241-ppp.3menatwork.com [72.0.210.241]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 9573420DC3 for <multrans@ietf.org>; Sat, 12 Nov 2011 09:52:15 -0500 (EST)
Message-ID: <4EBE8820.605@viagenie.ca>
Date: Sat, 12 Nov 2011 09:52:16 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc15 Lightning/1.0b3pre Thunderbird/3.1.10
MIME-Version: 1.0
To: multrans@ietf.org
References: <C0E0A32284495243BDE0AC8A066631A80C1E05D0@szxeml526-mbs.china.huawei.com> <BLU0-SMTP24236B87B5A606110FF802D8DD0@phx.gbl> <004d01cca0d0$e72adf10$b5809d30$@com>
In-Reply-To: <004d01cca0d0$e72adf10$b5809d30$@com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [multrans] link to meeting slides for multrans BoF
X-BeenThere: multrans@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss the work of IPv4-IPv6 multicast." <multrans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multrans>, <mailto:multrans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multrans>
List-Post: <mailto:multrans@ietf.org>
List-Help: <mailto:multrans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multrans>, <mailto:multrans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Nov 2011 14:52:47 -0000

Dan Wing wrote, on 11/11/2011 07:20 PM:
> Slide 7 says "Assuming AF1 is an ALG".  My comment:  don't build a system
> requiring an ALG.

We need to be careful here. There are two types of ALGs: transparent and
non-transparent (from RFC2101). Only the transparent ALG is "evil". A
non-transparent ALG, one that operates within the boundaries of an application
protocol (e.g. a SIP B2BUA, an HTTP proxy), can be a fine, recommendable
transition mechanism.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

v2.23.0 | Report a Bug | By Email