From behave-bounces@ietf.org  Sat Aug  2 10:09:20 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE23A3A690A;
	Sat,  2 Aug 2008 10:09:20 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 455F23A68D6
	for <behave@core3.amsl.com>; Sat,  2 Aug 2008 10:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FRT_STOCK2=3.988, RCVD_IN_DNSWL_MED=-4]
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 u1wnowg9rqiE for <behave@core3.amsl.com>;
	Sat,  2 Aug 2008 10:09:19 -0700 (PDT)
Received: from submit-tmp.sysedata.no (submit-tmp.sysedata.no [195.159.29.133])
	by core3.amsl.com (Postfix) with ESMTP id AEF3F3A690A
	for <behave@ietf.org>; Sat,  2 Aug 2008 10:09:18 -0700 (PDT)
Received: from [83.70.179.196] (helo=[172.16.16.249])
	by submit-tmp.sysedata.no with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.69) (envelope-from <aeh@db.org>)
	id 1KPKbi-0003md-W2; Sat, 02 Aug 2008 19:09:31 +0200
Message-ID: <48949422.4080103@db.org>
Date: Sat, 02 Aug 2008 18:06:42 +0100
From: "Alfred E. Heggestad" <aeh@db.org>
User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
In-Reply-To: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi

please see inline for my comments:


Philip Matthews wrote:
> There was an ad-hoc meeting on TURN  on Wednesday, July 31. During this 
> meeting, all the open issues affecting TURN were discussed and proposals 
> for how to resolve them reached. Jonathan and I then held a phone call 
> to discuss and in a couple of cases made minor tweaks. This e-mail 
> documents the proposed resolutions. Please comment if you are not happy 
> with any of these.
> 
>    1.  Detecting in-use channels.  Do we need a way for a client to
>        determine if a channel is currently bound?  Right now, the only
>        way is to try to bind it to an address.
> 
> This issue was prompted by concerns that the client and server might get 
> out-of-sync over which channels were bound. A concrete example of this 
> concern was when a client retransmitted a ChannelBind msg over UDP. If 
> the first transmission generated a failure response, but the second 
> generated a success response, then the client would believe that the 
> channel was not bound, but the server would believe the channel is bound.
> 
> The proposed resolution to this issue is to not add any way for the 
> client to determine which channels are bound, but to add text explicitly 
> saying that a client should abandon an allocation if it receives an 
> error response to a ChannelBind command. The idea is that any mismatch 
> between the client and the server in this area is very serious, and 
> starting over is the best way to recover.
> 

I dont see any need for detecting in-use channels.

the TURN client is controlling which channels are in use, and the
chances of a ChannelBind error response is very low.


> -- 
> 
>    2.  Public TURN servers.  The spec currently hints (but does not say
>        anything solid) that the way to run a publicly-accessable TURN
>        server is to not require authentication.  But perhaps a better
>        way is to require authentication but have some unspecified method
>        to allow any user to create an account on the server.
> 
> After discussion in the ad-hoc, we propose to say nothing about this. 
> The current text, which does really say anything about this, would 
> remain unchanged. The rationale is that this is a protocol document, not 
> an operational guidance document.
> 

Fully agree


> -- 
> 
>    3.  IPv6.  Currently, TURN supports IPv4-to-IPv4 relaying, and IPv6-
>        to-IPv6 relaying, but does not support IPv4-to-IPv6 relaying.  To
>        ensure this, a server requires that the family of the relayed
>        address match that of the 5-tuple as seen by the server.
>        However, some people would like to see a different rule.
> 
> The proposed resolution is to move the specification of IPv6-to-IPv6, 
> IPv4-to-IPv6, and IPv6-to-IPv4 relaying to draft-ietf-behave-turn-ipv6. 
> The base TURN specification would handle only IPv4-to-IPv4 relaying. The 
> base spec would say that the server address and all relayed addresses 
> must be IPv4 addresses.
> 
> This proposal ensures that client can know in advance what family (v4 or 
> v6) the relayed-transport-address returned by the server will always be 
> of. Some people had objected to the scheme in TURN-09 because the client 
> might send the Allocate request over IPv6, but unbeknownst to the 
> client, the request might pass through a NAT64 and arrive at the server 
> at an IPv4 address. If this happened, the client would get back an IPv4 
> relayed-transport-address when it really wanted an IPv6 
> relayed-transport-address. This proposal addresses their concern, while 
> also moving all the complexity around IPv6 and IPv4 <-> IPv6 to 
> draft-ietf-behave-turn-ipv6, where we have more time to study it and get 
> it right.
> 

Agreed.


> -- 
> 
>    4.  ALTERNATE-SERVER and Anycast.  The details of ALTERNATE-SERVER
>        support are still under discussion.  In particular, some people
>        would like to use ALTERNATE-SERVER to support anycast discovery
>        of a TURN server.
> 
> The proposed resolution is as follows:
> a) The TURN spec would allow the use of ALTERNATE-SERVER in replies to 
> Allocate requests. Furthermore, the text would override the STUN spec 
> and allow the use of ALTERNATE-SERVER in unauthenticated Allocate error 
> responses. If the client receives such a response, then the client 
> SHOULD retry the Allocate transaction with the new address. However, the 
> client MUST check that the realm value received back from the new server 
> is as expected and must use the same username and password as it would 
> have with the original server. In practice, this means that the client 
> must have known in advance what realm, username and password to use with 
> the original server, and uses these same values with the alternate 
> server. With this check, the client can ensure that the original and 
> alternate server are part of the same authentication group.
> b) The spec would NOT go into detail on how this mechanism can be used 
> to do anycast discovery. This would be left to another document.
> 
> In summary, the spec would provide the basic pieces required, but would 
> not go into details on how to use those pieces.
> 

I dont have any opinion about this..


> -- 
> 
>    5.  Authenticated Permission Refresh.  Currently, permissions can be
>        refreshed by unauthenticated Send indications and ChannelData
>        messages.  Some have suggested that this is a security issue.
> 
> The discussion of this issue at the BEHAVE meeting on Tuesday was 
> inconclusive. At the ad-hoc, there was further discussion and it was 
> realized that the attack described in the slides presented at the BEHAVE 
> meeting was easier to perform that we realized earlier. Given this 
> realization, the people at the ad-hoc meeting agreed on the following 
> (options 3 and 4 combined from the slides):
> a) In addition to a Send indication, TURN will support a Send 
> request/response transaction.
> b) Permissions will no longer be installed or refreshed by Send 
> indications or ChannelData msgs. Instead, permissions will be installed 
> or refreshed by ChannelBind transactions (as in turn-09) and by the new 
> Send request/response transaction. Since both of these are 
> request/response, they can be authenticated.
> c) The semantics of the new Send request/response is very similar to the 
> existing Send indication: it would take the same attributes, etc. 
> Specifically, it would have two forms: one with and one without the DATA 
> attribute; the 'without' form would only install or refresh permissions, 
> while the 'with' form would also send data.
> d) In addition, the client would check that Data messages are being 
> received from peer with which it thinks it has a permission. If the 
> client believes there is no permission, the client would discard the data.
> 

I will strongly suggest that any protocol changes to solve this, is
carefully reviewed by experts in this working group. I have been running
the current permission/channel mechanism (defined in turn-07/08/09)
for a while now, and it shows that it is very elegant and clean and robust.
I have not seen any problems with it in deployment.

I am very worried that if we change the turn-spec to add Send Request/Response,
we will indirectly add new problems that we did not think of.

for each TURN allocation, both the client and the server must maintain a list
of channels in use. The same thing would then also apply for Permissions, as
both client and server must maintain a list of permissions (per alloation).
if we can live with the increased security of checking permissions in the
TURN client (SHOULD-strength?), then I would be voting for this solution.



> 
> -- 
> 
>    6.  PMTUD for non-preserving allocations.  Some people would like a
>        way to do PMTUD even if the allocation is non-preserving, and
>        have suggested that a way for the client to indicate to the
>        server (in a Send indication) that the DF bit should be set when
>        sending to the peer might allow this.
> 
> There was hot discussion of this issue at the ad-hoc. Finally, it was 
> agreed that the mechanism suggested by Cullen would be added to the TURN 
> specification, to whit:
> a) A new attribute would be defined for use in a Send indication. If 
> this attribute is present, then the server would set the DF bit when 
> sending the UDP datagram to the peer.
> 

if this is really required, I would suggest moving the attribute/bit
to the allocate request instead. setting the DF-bit is normally done
when opening a socket (setsockopt IP_MTU_DISCOVER)

as a side note, it would be nice to have more fine-grained control
with how the allocation/server should behave. I mean instead of having
a bit-flag saying non-preserving/preserving, we could add more bits
which describe each feature for that allocation.

the client would request a feature by setting a bit to 1, the server
would include in the response which features it supports (0==disabled,
1==enabled).



> -- 
> 
>    7.  Security.  The security consideration section is out-of-date with
>        the changes to the rest of the draft, and it has been suggested
>        that TURN might require TLS to provide proper security.  Updating
>        the security consideration section will answer this question.
> 
> The above changes fix all known security holes. Never-the-less, the 
> authors plan to rewrite the security considerations section ASAP, which 
> would involve taking another hard look at TURN security.
> 

[...]


/alfred

> Comments?
> 
> - Philip
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun Aug  3 03:51:34 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C6C173A683B;
	Sun,  3 Aug 2008 03:51:34 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 538943A682C
	for <behave@core3.amsl.com>; Sun,  3 Aug 2008 03:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.765
X-Spam-Level: 
X-Spam-Status: No, score=-101.765 tagged_above=-999 required=5
	tests=[AWL=-0.500, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334,
	J_BACKHAIR_12=1, USER_IN_WHITELIST=-100]
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 VjSdStnhHj84 for <behave@core3.amsl.com>;
	Sun,  3 Aug 2008 03:51:30 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 7CF903A6BEB
	for <behave@ietf.org>; Sun,  3 Aug 2008 03:50:09 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id 0C2237F0314; Sun,  3 Aug 2008 10:50:35 +0000 (UTC)
Received: from [192.168.1.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id 5ACEE7F0314;
	Sun,  3 Aug 2008 10:50:34 +0000 (UTC)
Message-ID: <48958D79.10209@acm.org>
Date: Sun, 03 Aug 2008 03:50:33 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: "Alfred E. Heggestad" <aeh@db.org>
References: <488EC549.6010903@db.org>
In-Reply-To: <488EC549.6010903@db.org>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] SASLprep password
	in	draft-ietf-behave-stun-test-vectors-03.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Alfred E. Heggestad wrote:
> hi
>
>
> I have a small comment on draft-ietf-behave-stun-test-vectors-03.txt
>
>
> Section 2.4 says:
>
>       Password: "TheA<U+00AD>M<U+00AA>tr<U+2168>" (without quotes) before
>             SASLprep processing
>
>
> I am not sure how to interpret this, would it be possible to also
> include a binary string containing the password (after SASLprep) ?
>

The <U+00AD> notation describes a Unicode codepoint.  This notation has
the advantage of been independent of the computer language.  The
problem, I think, of using a binary form is that it is depending of the
way characters are encoded in a specific platform, programming language
and API (UTF-16, UTF-8, sequence of 16 bit integer, etc...).

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 05:42:31 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 87CE628C216;
	Mon,  4 Aug 2008 05:42:31 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F085828C21B
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 05:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level: 
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.030, 
	BAYES_00=-2.599, NO_RELAYS=-0.001]
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 IaC+SOJj16jw for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 05:42:28 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id C384F28C20F
	for <behave@ietf.org>; Mon,  4 Aug 2008 05:42:27 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m74Cg5Pv010266
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 4 Aug 2008 14:42:06 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <E366679E-1483-486F-A2E6-F2EBC3959827@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <0B9335C7-640B-4094-844F-0ABDD4825186@cisco.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 4 Aug 2008 14:42:27 +0200
References: <20080707024501.9FEDD3A69BC@core3.amsl.com>
	<0B9335C7-640B-4094-844F-0ABDD4825186@cisco.com>
X-Mailer: Apple Mail (2.926)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] draft-jennings-behave-nat6-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 7 jul 2008, at 6:06, Cullen Jennings wrote:

> A draft related to the nat64 and nat46 topic ....

    A record query, and then it composes a v6 address formed by  
putting a
    ::FFFF/96 prefix before the v4 address.

What you wrote here is the prefix formed by the 96 most significant  
bits of the address 0:0:0:0:0:0:0:ffff = 0:0:0:0:0:0. I don't think  
that's what you had in mind.

Also note that using the v4-mapped prefix (::ffff:0:0/96) would  
require changes to all major OSes, as they will only generate IPv4  
packets towards this destination prefix and not IPv6 packets. (See  
what I wrote on the int area list.)

You put the burden of being reachable for IPv4 clients on the IPv6  
server. This makes sense in the current situation where being  
connected to the internet means having IPv4 connectivity. However, it  
doesn't solve the case where IPv4 clients want to connect to IPv6  
servers that _don't_ have an IPv4 address similar how NAT64 allows  
IPv6 clients to connect to IPv4 servers that don't have an IPv6 address.

    Typically a STUN server would be used.  Note that a
    UDP transaction to a STUN server will allocate a mapping that can be
    used for incoming TCP connections.  The NAT is required to run a  
STUN
    server on the external side at the address ::FFFF:127.0.0.1 on the
    default STUN port so the server will always be able to find a STUN
    server if it is behind a NAT.

Yes, something like this makes sense.

    The servers that tend to be popular to run behind NATs are mostly  
P2P
    applications, such as file sharing and VoIP.

I would prefer to stay away from the word "server" for this case, and  
reserve that for the simple client/server model servers.

    Note that any IP options are lost in this process; also, as
    defined in UDP and TCP, new checksums will be computed.

The fragment header needs to be handled.

I would say that the checksums are updated. I.e., if a packet comes in  
with an incorrect checksum, it's not the NAT's job to detect that, let  
alone correct it. The checksum should just be incrementally updated to  
reflect the modifications to the packet.

I think the discussion of MTU/fragmentation related issues is useful,  
apparently we never put this in the NAT64 document...

However:

    The NAT MUST support reassembly of fragmented packets when the
    packets are received in order, but support for out of order  
fragments
    is OPTIONAL.

@ NAT64 co-authors:  :-)

    If the NAT receives a v4 packet with the do not fragment bit set, it
    MUST NOT forward it if the MTU of the v6 link would require the
    packet to be fragmented, and the NAT MUST NOT include a fragment
    header in the v6 packet.

Why MUST? SHOULD is more than strong enough.

    If the NAT receives a v4 packet that does
    not have the do not fragment bit set, then the packet, when
    forwarded, MUST include a fragment header

Huh? Do you mean that you translate the fragments rather than  
reassemble and refragment?

    When the NAT receives a v6 packet without a fragment header, it MUST
    set the do not fragment bit in any v4 packets

I guess this is to allow for path MTU discovery. However, as discussed  
in the meeting last week, IPv6 hosts don't believe in maximum packet  
sizes smaller than 1280 bytes so this won't work if the IPv4 MTU is  
smaller than 1260 bytes. Solution:

- set the DF bit to 0 for IPv6 packets <= 1280 bytes
- set the DF bit to 1 for IPv6 packets > 1280 bytes

(May want to mention at some point that sending ICMP "too big"  
messages is a MUST.)

    NAT processing of ICMP errors is complicated and of very limited
    value; for that reason forwarding ICMP error messages is OPTIONAL.
    Processing to allow ping and traceroute through the NAT is also
    OPTIONAL

Disagree. You MUST be able to translate ICMP to support path MTU  
discovery anyway, so anything that only requires straight ICMP  
translation can be easily supported. This includes various  
unreachables, which are important to avoid application timeouts in  
certain cases. Pings and probably even traceroutes should work without  
issues with this type of translation.

Telling vendors that it's ok to ignore ICMP is not a message the IETF  
should be sending, especially because users won't be able to vote with  
their feet by selecting a different vendor for these types of  
translators as they're deployed by service providers.

    UDP is the new thin waist of the internet.  IPsec over UDP will  
work,
    but other forms of IPsec will generally not work in a reliable way.

Host changes are necessary on at least one end because of the non- 
matching IP versions that the translator can't change because of  
authentication and/or encryption.

5.8.  DCCP, SCTP, etc

    The strong temptation is to extend this specification to support
    these protocols.  However, that path is probably doomed and would
    just add needless complexity.  The issue is, if there were ever any
    applications to use these protocols, the applications would probably
    want to work through the existing deployed v4 to v4 NATs, which do
    not support these transports.  As a result the new transports are  
not
    useful to applications unless they are adapted to work over existing
    NATs - most commonly by running them over UDP.

I agree that when building a hack like NAT64 to get existing stuff to  
work, it's not an obvious choice to future-proof the hack.

Note that SCTP won't work by just encapsulating it in UDP because of  
its address management.

    This approach does not require any DNS ALG.  The downside is that  
the
    servers in the 4 to 6 case need to discover and advertise their v4
    addresses, rather than letting the NAT and DNS automatically
    coordinate them.  One of the upsides of this design is that DNSSEC
    can work

No DNS ALG = broad definition, this includes the DNS64 functionality  
from our NAT64 draft (although that's not an ALG). With the v4-mapped  
prefix hosts will automatically create the necessary IPv6 addresses  
from A records but as stated before, those addresses won't generate  
IPv6 packets. So host changes are required one way or another if  
synthetic AAAA records are out.

    FTP.  There is no need for an FTP ALG; use EPSV.

I don't have any numbers, but I'm pretty sure there are still  
significant numbers of FTP servers that only support PASV out there.  
However, requiring those to be updated is preferable to implementing  
ALGs, IMO. So agree.

    DHCP is very useful for the automated configuration of many things
    beyond IP addresses. [[ TODO should any particular DHCP things be
    required]]

Disagree on principle (RAs are the One True Way), and disagree that  
it's useful to mention DHCP in the helper services part of this  
document. Not even wasting key clicks on 7.4

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 05:46:07 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33D6D3A6CA5;
	Mon,  4 Aug 2008 05:46:07 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9BA93A6CA0
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 05:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.028, 
	BAYES_00=-2.599, NO_RELAYS=-0.001]
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 8qesXbQd5fTO for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 05:46:06 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 7E3D83A6A09
	for <behave@ietf.org>; Mon,  4 Aug 2008 05:46:05 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m74Ck74Y010357
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 4 Aug 2008 14:46:08 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <8DD7A6C3-0D1E-446A-B65B-C8D0C16D3802@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <487E7EBE.7060308@gmail.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 4 Aug 2008 14:46:29 +0200
References: <20080707024501.9FEDD3A69BC@core3.amsl.com>	<0B9335C7-640B-4094-844F-0ABDD4825186@cisco.com>	<01cb01c8e0a0$25de3d50$c2f0200a@cisco.com>	<9E6E0AF5-E64A-47F3-A886-0FB710375490@cisco.com>
	<108c01c8e15f$7d8d63e0$c2f0200a@cisco.com>
	<487E7EBE.7060308@gmail.com>
X-Mailer: Apple Mail (2.926)
Cc: 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] draft-jennings-behave-nat6-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 17 jul 2008, at 1:05, Brian E Carpenter wrote:

> Conceptually, I definitely prefer the draft-bagnulo-behave-nat64
> model (which I think of as a SIIT protocol translator in series
> with a pretty much industry-standard IPv4-IPv4 NAT).

This is not really true: a NAT64 translator (as well as a dual stack  
"lite" carrier grade NAT) demultiplex on the IPv6 address, not on a  
private IPv4 address. This is a small but important difference that  
makes these translators much cleaner and more capable than regular  
NAT44 translators.

> I think the draft-jennings-behave-nat6 approach has the negative
> characteristic of importing NAT-related issues into IPv6-related
> code, and that is something we want to avoid if we can.

Agree.

However, now that the IPv6-firewall-enabled-by-default cat is out of  
the bag, techniques like ICE are probably needed to make IPv6-IPv6  
peer-to-peer sessions more robust. ICE _should_ be able to work across  
the IPv4/IPv6 boundary, so it doesn't seem to onerous to expect ICE  
support for IPv6 peer-to-peer applications.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 05:53:22 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C93DE3A6953;
	Mon,  4 Aug 2008 05:53:22 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80F343A6953
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 05:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.027, 
	BAYES_00=-2.599, NO_RELAYS=-0.001]
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 LdqE6PQTqCnY for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 05:53:20 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 380323A68F2
	for <behave@ietf.org>; Mon,  4 Aug 2008 05:53:19 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m74CrKj1010453
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 4 Aug 2008 14:53:21 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <A51759C2-DC5E-4BAD-B4CA-421CD73CDEF6@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Philip Matthews <philip_matthews@magma.ca>
In-Reply-To: <9494ECB7-1994-4870-8221-29A307AEA536@magma.ca>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 4 Aug 2008 14:53:41 +0200
References: <E9CACA3D8417CE409FE3669AAE1E5A4F04587E87AC@NA-EXMSG-W601.wingro
	up.windeploy.ntdev.microsoft.com><487F0EB0.80505@it.uc3m.es><E9CACA3D8417C
	E	409FE3669AAE1E5A4F04588B8CEA@NA-EXMSG-W601.wingroup.windeploy.ntdev.micro
	so	ft.com><4EF3E72F-D601-4ED6-92C3-6F6F6C352755@muada.com>
	<E9CACA3D8417CE409FE3669AAE1E5A4F04588B93B7@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<48873682.2000100@it.uc3m.es>
	<E9CACA3D8417CE409FE3669AAE1E5A4F04589BE177@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<9494ECB7-1994-4870-8221-29A307AEA536@magma.ca>
X-Mailer: Apple Mail (2.926)
Cc: "behave@ietf.org" <behave@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] Comments on draft-bagnulo-behave-nat64-00
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 29 jul 2008, at 4:09, Philip Matthews wrote:

> However, if AAAA records are synthesized using a single prefix, as  
> Dave is suggesting, then I think it is much harder to ensure that L  
> always uses the same NAT64 device.

> To be more precise, what we want is that all traffic from L uses one  
> NAT64, but all traffic from another node M uses a different NAT64,  
> etc, so that there is more-or-less an even assignment of nodes to  
> NAT64 devices, with one node always using the same NAT64.

The problem here is using the words "all" and "always".

It's fairly trivial to build a setup where packets from the same  
source consistently arrive at the same destination, even if multiple  
destinations share an address. As long as the routing remains the  
same. When there is an outage that leads the routing protocols to  
select new paths, packets may end up at a different instance of the  
address in question.

However, this is as much a feature as a bug: rather than talking to a  
dead translator and/or over dead links, the user gets to talk to a  
working translator.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 05:58:18 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67D6F28C24A;
	Mon,  4 Aug 2008 05:58:18 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A5C928C24A
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 05:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.026, 
	BAYES_00=-2.599, NO_RELAYS=-0.001]
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 nEkWPHgdG5wH for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 05:58:16 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 4BCDD28C249
	for <behave@ietf.org>; Mon,  4 Aug 2008 05:58:16 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m74CwJHl010570
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 4 Aug 2008 14:58:20 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <AD9F35D0-D386-496A-AFFE-63D4BCFDB9A5@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Dave Thaler <dthaler@windows.microsoft.com>
In-Reply-To: <E9CACA3D8417CE409FE3669AAE1E5A4F0458A9428F@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 4 Aug 2008 14:58:40 +0200
References: <alpine.LRH.1.10.0807291841150.27051@netcore.fi>
	<FAB65D70-B3B2-405C-AE57-536B3D02DAED@magma.ca>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0458A9428F@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: Apple Mail (2.926)
Cc: "behave@ietf.org" <behave@ietf.org>,
	Philip Matthews <philip_matthews@magma.ca>,
	Pekka Savola <pekkas@netcore.fi>
Subject: Re: [BEHAVE] NAT6 fragmentation discussion
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 30 jul 2008, at 1:39, Dave Thaler wrote:

> That's why we have RFC 4890 ("Recommendations for Filtering ICMPv6
> Messages in Firewalls").  Section 4.3.1 ("Traffic That Must Not Be  
> Dropped")
> includes:

>>  o  Packet Too Big (Type 2)

> And also RFC 4821 ("Packetization Layer Path MTU Discovery")
> that specifies PMTU discovery for TCP without relying on ICMP.

RFC 4821 doesn't get anyone off the hook for filtering ICMP.

Are there _any_ implementations of 4821 available in the wild, let  
alone in common OSes?
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 06:19:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CDEC128C280;
	Mon,  4 Aug 2008 06:19:26 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 039DF28C280
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 06:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level: 
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[AWL=0.018, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 FefgZwF9htvD for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 06:19:25 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id C472C28C261
	for <behave@ietf.org>; Mon,  4 Aug 2008 06:19:24 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m74DJeMh029019; Mon, 4 Aug 2008 16:19:42 +0300
Received: from vaebh103.NOE.Nokia.com ([10.160.244.24]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 4 Aug 2008 16:18:55 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 4 Aug 2008 16:18:54 +0300
Received: from esdhcp04041.research.nokia.com ([172.21.40.41]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 4 Aug 2008 16:18:54 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 4 Aug 2008 16:18:58 +0300
User-Agent: KMail/1.9.9
References: <alpine.LRH.1.10.0807291841150.27051@netcore.fi>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0458A9428F@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<AD9F35D0-D386-496A-AFFE-63D4BCFDB9A5@muada.com>
In-Reply-To: <AD9F35D0-D386-496A-AFFE-63D4BCFDB9A5@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808041618.59336.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 04 Aug 2008 13:18:54.0823 (UTC)
	FILETIME=[A5124770:01C8F634]
X-Nokia-AV: Clean
Cc: Pekka Savola <pekkas@netcore.fi>,
	Philip Matthews <philip_matthews@magma.ca>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] NAT6 fragmentation discussion
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Monday 04 August 2008 15:58:40 ext Iljitsch van Beijnum, you wrote:
> RFC 4821 doesn't get anyone off the hook for filtering ICMP.

Not sure what you mean. But this is a real-life problem, e.g. when the "las=
t =

mile" link uses PPPoE or PPPoA (MTU =3D 1492) and the LAN uses Fast Etherne=
t =

(MTU =3D 1500).

> Are there _any_ implementations of 4821 available in the wild, let
> alone in common OSes?

I believe Linux does not do it (for TCP), though it has explicit support fo=
r =

UDP(/UDP-Lite) applications to do it at layer-7.

However, NAT box typically do TCP MSS clamping. This works around the probl=
em =

if the shortest MTU hop sits next to a TCP MSS clamping device and/or one o=
f =

the end point. This is almost always true. If not true, "the Internet does =

not work" is a strong argument to make it true ;) Obviously, this only work=
s =

for TCP, and will break with any other transport protocol, including UDP or =

UDP-encapsulated transport protocol.


-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 06:54:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DABAF3A69FC;
	Mon,  4 Aug 2008 06:54:47 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 500BA3A680B
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 06:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5
	tests=[AWL=-0.125, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	NO_RELAYS=-0.001]
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 IOdh3poXANWA for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 06:54:44 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 0F4C528C245
	for <behave@ietf.org>; Mon,  4 Aug 2008 06:54:43 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m74DsjUM011339
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 4 Aug 2008 15:54:46 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <AD83CA47-713F-4232-984D-431969392806@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200808041618.59336.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 4 Aug 2008 15:55:06 +0200
References: <alpine.LRH.1.10.0807291841150.27051@netcore.fi>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0458A9428F@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<AD9F35D0-D386-496A-AFFE-63D4BCFDB9A5@muada.com>
	<200808041618.59336.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.926)
Cc: Pekka Savola <pekkas@netcore.fi>, behave@ietf.org,
	Philip Matthews <philip_matthews@magma.ca>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] NAT6 fragmentation discussion
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 4 aug 2008, at 15:18, R=E9mi Denis-Courmont wrote:

>> RFC 4821 doesn't get anyone off the hook for filtering ICMP.

> Not sure what you mean.

That you can't say "we can filter ICMP because there's RFC 4821" or  =

"we can filter ICMP because we implement RFC 4821". (The other side  =

may still depend on existing PMTUD.)

> However, NAT box typically do TCP MSS clamping.

Yes, we should probably specify reducing the advertised MSS for TCP in  =

the NAT64 draft to accommodate for the difference in header size  =

between IPv4 and IPv6.

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 07:11:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7444D3A6CBE;
	Mon,  4 Aug 2008 07:11:49 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 03E993A6CBE
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 07:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.282
X-Spam-Level: 
X-Spam-Status: No, score=-6.282 tagged_above=-999 required=5 tests=[AWL=0.017, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 MIM-mQ7PDaSg for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 07:11:48 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 064663A68D4
	for <behave@ietf.org>; Mon,  4 Aug 2008 07:11:47 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m74EBuRu020466; Mon, 4 Aug 2008 09:12:13 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 4 Aug 2008 17:11:55 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 4 Aug 2008 17:11:32 +0300
Received: from esdhcp04041.research.nokia.com ([172.21.40.41]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 4 Aug 2008 17:11:32 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: "ext Iljitsch van Beijnum" <iljitsch@muada.com>
Date: Mon, 4 Aug 2008 17:11:36 +0300
User-Agent: KMail/1.9.9
References: <alpine.LRH.1.10.0807291841150.27051@netcore.fi>
	<200808041618.59336.remi.denis-courmont@nokia.com>
	<AD83CA47-713F-4232-984D-431969392806@muada.com>
In-Reply-To: <AD83CA47-713F-4232-984D-431969392806@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808041711.37261.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 04 Aug 2008 14:11:32.0702 (UTC)
	FILETIME=[FF505FE0:01C8F63B]
X-Nokia-AV: Clean
Cc: Pekka Savola <pekkas@netcore.fi>, behave@ietf.org,
	Philip Matthews <philip_matthews@magma.ca>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] NAT6 fragmentation discussion
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Monday 04 August 2008 16:55:06 ext Iljitsch van Beijnum, you wrote:
> On 4 aug 2008, at 15:18, R=E9mi Denis-Courmont wrote:
> >> RFC 4821 doesn't get anyone off the hook for filtering ICMP.
> >
> > Not sure what you mean.
>
> That you can't say "we can filter ICMP because there's RFC 4821" or
> "we can filter ICMP because we implement RFC 4821". (The other side
> may still depend on existing PMTUD.)

Ok. In principles, I have to agree that filtering ICMP is bad. And filterin=
g =

Packet Too Big "violates" RFC4890 (which is however only _Informational_). =
In =

practice however, filtering ICMPv4 is common practice. Any NAT64 solution =

that fails to account for this will dramatically fail in real deployments.

> > However, NAT box typically do TCP MSS clamping.
>
> Yes, we should probably specify reducing the advertised MSS for TCP in
> the NAT64 draft to accommodate for the difference in header size
> between IPv4 and IPv6.

The IPv6 end of the TCP session will negotiate a small enough MSS to accoun=
t =

for the extra 20 bytes of IPv6 as part of its normal TCP stack operation.
MSS clamping is an ugly-but-functional hack in case of mismatching layer-2 =

maximum frame payload sizes. It is not at all needed nor useful with regard=
s =

to layer-3 mismatching packet payload sizes, as far as I can tell.


-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 18:41:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A28C33A691C;
	Mon,  4 Aug 2008 18:41:26 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51CB93A6932
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 18:41:25 -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 gz3Z7z2nQVc2 for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 18:41:24 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230])
	by core3.amsl.com (Postfix) with ESMTP id 49F893A6878
	for <behave@ietf.org>; Mon,  4 Aug 2008 18:41:24 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so1989549rvf.49
	for <behave@ietf.org>; Mon, 04 Aug 2008 18:41:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:content-type
	:content-transfer-encoding;
	bh=bQzHlkJlUbdwC9LFyZ5wEIwH1C/E+XSI2XzJMdbJrwg=;
	b=iBYDMjWgyIhjJHuJR6GJhxZT6lrRxyvmVC1AtyOj7wWDr+l/Qgpb14BvmbX6/PLrMM
	VBdWKOAVtAI/2wMqaW0dFcCV3AdBYAzfgOz8OKB29Q1WZXHxhAVhSEYshM2GTYENUtNG
	z64QKGamCTGR3JtX3dEwayfd2VF8k0ktsiLk4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:content-type:content-transfer-encoding;
	b=OGZ3kj1jpcEUi5E4TJp/Boi9SUDE/6awg/QX3TeRsBH7JJwY4GECue0tSb2FO+z0lX
	hQY1QfWaQVZodU6hx8cZ+cbCzdUgEoz5u/7t9Uw9BnSnp0TwUb0hzA03iAw0zH7kP0z6
	wI4wEbZDwPF+Q6tmApsyYtK62258tNdczY1Ek=
Received: by 10.141.210.21 with SMTP id m21mr7882876rvq.23.1217900480367;
	Mon, 04 Aug 2008 18:41:20 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124])
	by mx.google.com with ESMTPS id k2sm8321807rvb.4.2008.08.04.18.41.18
	(version=SSLv3 cipher=RC4-MD5); Mon, 04 Aug 2008 18:41:19 -0700 (PDT)
Message-ID: <4897AFC0.9080007@gmail.com>
Date: Tue, 05 Aug 2008 13:41:20 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: behave@ietf.org
Cc: Richard Nelson <richardn@cs.waikato.ac.nz>, int-area@ietf.org,
	Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

In case people aren't already aware of it, I think the work at the
second URL below is very interesting in discussing the possible
implications of CGN, and in particular the number of outbound and
inbound ports needed per active host.

(Sorry about cross-posting, please feel free to trim any replies.)

    Brian

-------- Original Message --------
Subject: Re: [nznog] Importance of end-to-end IPv4 - research - please help
Date: Tue, 05 Aug 2008 12:20:13 +1200
From: Richard Nelson <richardn@cs.waikato.ac.nz>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Shane Alcock <salcock@cs.waikato.ac.nz>
References: <489794A3.2080003@cs.waikato.ac.nz> <48979977.2030800@gmail.com>

Yes that is fine.  Glad to have the work used.  Point out that it was
sponsored by Alcatel and presented by David Miles at Apricot this year.

If you are interested in the source of the data a description of the
trace is at http://www.wand.net.nz/wits/localisp/b/3/

Richard.

Brian E Carpenter wrote:
> Shane,
>
>   
>> More detailed results (plus pretty graphs!) can be found at 
>> http://www.wand.net.nz/~spa1/someisp/flow_counting/result_page.html#inbound
>>     
>
> This is wonderful information. Are you watching the current discussion
> in the IETF about carrier grade NAT? Do you have any objection to
> me forwarding the URL there?
>
>     Brian
>   


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug  4 19:10:38 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38B833A6A26;
	Mon,  4 Aug 2008 19:10:38 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5326E3A6A26
	for <behave@core3.amsl.com>; Mon,  4 Aug 2008 19:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.064
X-Spam-Level: 
X-Spam-Status: No, score=-110.064 tagged_above=-999 required=5
	tests=[AWL=0.235, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 NpayPHbpUJJP for <behave@core3.amsl.com>;
	Mon,  4 Aug 2008 19:10:34 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215])
	by core3.amsl.com (Postfix) with ESMTP id C3C1D3A69D3
	for <behave@ietf.org>; Mon,  4 Aug 2008 19:10:34 -0700 (PDT)
Received: from tk1-exhub-c101.redmond.corp.microsoft.com (157.54.46.185) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.1.251.2; Mon, 4 Aug 2008 19:10:53 -0700
Received: from tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com
	(157.54.18.33) by tk1-exhub-c101.redmond.corp.microsoft.com
	(157.54.46.185)
	with Microsoft SMTP Server id 8.1.240.5; Mon, 4 Aug 2008 19:10:53 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com
	([fe80::8de9:51a2:cd62:f122]) by
	tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.33])
	with mapi; Mon, 4 Aug 2008 19:10:53 -0700
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Pekka Savola <pekkas@netcore.fi>, =?iso-8859-1?Q?R=E9mi_Denis-Courmont?=
	<remi.denis-courmont@nokia.com>
Date: Mon, 4 Aug 2008 19:10:51 -0700
Thread-Topic: [BEHAVE] Comments on draft-bagnulo-behave-nat64-00
Thread-Index: Acjxd1Zc/3qrzdxUTCKDeTeof2DyEQFJtbyQ
Message-ID: <E9CACA3D8417CE409FE3669AAE1E5A4F0458B6B446@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <E9CACA3D8417CE409FE3669AAE1E5A4F04587E87AC@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<4EF3E72F-D601-4ED6-92C3-6F6F6C352755@muada.com>
	<E9CACA3D8417CE409FE3669AAE1E5A4F04588B93B7@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<200807291459.58040.remi.denis-courmont@nokia.com>
	<alpine.LRH.1.10.0807291521150.22317@netcore.fi>
In-Reply-To: <alpine.LRH.1.10.0807291521150.22317@netcore.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>,
	"philip_matthews@magma.ca" <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] Comments on draft-bagnulo-behave-nat64-00
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org



> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Pekka Savola
> Sent: Tuesday, July 29, 2008 5:33 AM
> To: R=E9mi Denis-Courmont
> Cc: behave@ietf.org; philip_matthews@magma.ca; Dave Thaler
> Subject: Re: [BEHAVE] Comments on draft-bagnulo-behave-nat64-00
>
> This is mainly directed at Dave, but I'm responding off Remi's comment,
>
> On Tue, 29 Jul 2008, R=E9mi Denis-Courmont wrote:
> > On Tuesday 22 July 2008 04:06:37 ext Dave Thaler, you wrote:
> >> If you have a v6-only network, then handing out a DNS64 server's
> >> address in DHCPv6 as the DNS server is the right thing.
> >>
> >> If you have a dual-stack network, then you'd really like to give
> >> v6-only hosts a DNS64 server (e.g., via DHCPv6), but give dual-stack
> >> hosts a DNS server.
>
> How does the operator configuring DNS, DHCPv6, and/or Router
> Advertisements know whether a host is v6-only or dual-stack?

In some cases, it's obvious, such as
a) when the DNS64 is close to the client, and it's on a v6-only network
that has hosts that aren't multi-homed (e.g. some cell phone networks).
This was picture 2 in Mark Townsley's INTAREA deck if I recall correctly.
b) when the DNS64 is close to the server, and the server network has
no public IPv4 addresses and hence all clients are logically v6-only
as far as connectivity to that network is concerned.  This was
picture 3 in Mark's INTAREA deck if I recall correctly.

This is why it's important to distinguish between common cases,
since there may be some scenarios that are simple.

> Note that a dual-stack host may also use DHCPv6 to request DNS server
> address information.  Such a host would probably also prefer those
> addresses over v4 DNS server addresses.
>
> Do we also need to care about a scenario which has v6-only network and
> NAT64, but the user configures a v4-over-v6 tunnel or v6-in-v6 VPN and
> has connectivity and name lookup capability beyond what's provided by
> the physical network operator?

Yes, that's logically equivalent to a multihomed host, which is a
valid scenario.

> > If we assume that all current v6-capable nodes are actually dual-
> stack...
> > could we do it so that:
> >
> > * On v6-only network, DNS64 is provisioned like normal (e.g. DHCPv6
> > and/or
> > SLAAC) as "the" DNS recursive server.
> >
> > * On a dual-stack network, DNS64 is provisioned with a *new*
> > DNS64-specific setting (e.g. an extension to DHCPv6), and normal DNS
> > is only provisioned via
> > IPv4 (e.g. DHCPv4).
>
> Trying to figure out if this has implications on the "thou shalt not
> modify hosts" requirement (when examining dual-stack nodes in
> particular) makes my head ache :-/

Depends on the scenario.  In all but one scenario (the greenfield
case as Alain put it), "don't modify hosts" is a requirement, at
least in my view.

-Dave

> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 02:23:22 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D869D3A6B20;
	Tue,  5 Aug 2008 02:23:22 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B8E63A6B20
	for <behave@core3.amsl.com>; Tue,  5 Aug 2008 02:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.42
X-Spam-Level: 
X-Spam-Status: No, score=-2.42 tagged_above=-999 required=5 tests=[AWL=-0.120, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 x3mTRd8+qfmt for <behave@core3.amsl.com>;
	Tue,  5 Aug 2008 02:23:21 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 2B24B3A6932
	for <behave@ietf.org>; Tue,  5 Aug 2008 02:23:20 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m759NO78040902
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 5 Aug 2008 11:23:25 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <39F68FE6-AECF-48BF-A66F-12857CC00B32@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200808041711.37261.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 5 Aug 2008 11:23:46 +0200
References: <alpine.LRH.1.10.0807291841150.27051@netcore.fi>
	<200808041618.59336.remi.denis-courmont@nokia.com>
	<AD83CA47-713F-4232-984D-431969392806@muada.com>
	<200808041711.37261.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.926)
Cc: Pekka Savola <pekkas@netcore.fi>, behave@ietf.org,
	Philip Matthews <philip_matthews@magma.ca>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] NAT6 fragmentation discussion
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 4 aug 2008, at 16:11, R=E9mi Denis-Courmont wrote:

> Ok. In principles, I have to agree that filtering ICMP is bad. And  =

> filtering
> Packet Too Big "violates" RFC4890 (which is however only  =

> _Informational_).

That's not relevant.

What's relevant is that the OS vendors have chosen to all enable PMTUD  =

by default and set the DF bit on all packets. (The latter was the big  =

mistake.) This means that filtering ICMP too bigs WILL break  =

connectivity which is NOT acceptable.

For IPv6 it's impossible to set DF to zero as there is no DF bit and  =

again, all implementers use PMTUD implicitly by sending packets larger  =

than 1280 bytes. So again, filtering ICMP breaks connectivity and is  =

therefore not acceptable.

Which means that all IETF standards and other documents MUST REQUIRE  =

that ICMP too big messages are NOT filtered.

> In
> practice however, filtering ICMPv4 is common practice.

I know behave has a tradition of looking at what's out there in the  =

real world, rather than what's in the standards, but in this case,  =

that's not a workable choice.

> Any NAT64 solution
> that fails to account for this will dramatically fail in real  =

> deployments.

NAT64 is not the place to compensate for bad ICMP filtering practices,  =

but it's certainly not the place to promote such practices, either.

That said, I'm not aware of anything in our draft (or any of the  =

others) that would break in addition to "normal" PMTUD breakage.

>> Yes, we should probably specify reducing the advertised MSS for TCP  =

>> in
>> the NAT64 draft to accommodate for the difference in header size
>> between IPv4 and IPv6.

> The IPv6 end of the TCP session will negotiate a small enough MSS to  =

> account
> for the extra 20 bytes of IPv6 as part of its normal TCP stack  =

> operation.
> MSS clamping is an ugly-but-functional hack

I guess in practice it would normally work. For instance, if the v4  =

side has a 1492-byte MTU so MSS =3D 1452 the IPv6 side will think it can  =

send 1452 + 60 =3D 1512-byte packets but it will of course send 1500- =

byte IPv6 packets which will be translated into 1480-byte IPv4 packets  =

so no problem.

But what if the v6 host and the translator support jumboframes and the  =

v6 host sends 1512-byte packets? Or if the translator reassembles IPv6  =

fragments before translating?

I think adjusting the MSS option in the v4->v6 direction makes the  =

most sense here, and it would be good to implement a knob for  =

operators to further reduce the MSS in both directions in the  =

translator if desired.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 02:40:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4289528C1A4;
	Tue,  5 Aug 2008 02:40:02 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F6243A6894;
	Tue,  5 Aug 2008 02:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.034, 
	BAYES_00=-2.599, NO_RELAYS=-0.001]
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 dY6OYi+TKcok; Tue,  5 Aug 2008 02:39:59 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 654F93A67EC;
	Tue,  5 Aug 2008 02:39:59 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m759dugI041505
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 5 Aug 2008 11:39:56 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4897AFC0.9080007@gmail.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 5 Aug 2008 11:40:17 +0200
References: <4897AFC0.9080007@gmail.com>
X-Mailer: Apple Mail (2.926)
Cc: Richard Nelson <richardn@cs.waikato.ac.nz>, int-area@ietf.org,
	behave@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 5 aug 2008, at 3:41, Brian E Carpenter wrote:

> In case people aren't already aware of it, I think the work at the
> second URL below is very interesting in discussing the possible
> implications of CGN, and in particular the number of outbound and
> inbound ports needed per active host.

Hm, it looks like the high water marks for TCP and UDP sessions per  
subscriber (including non-active subscribers) is around 20 and 40.

For our purposes we can probably assume that the UDP is lower than TCP  
because UDP in this is very likely mostly DNS which shouldn't have to  
go through a NAT64.

So that means a single IPv4 address can support about 3000 subscribers.

However, in the future it's likely that each subscriber will have a  
larger number of devices so we shouldn't be too surprised if this goes  
down.

I'd say based on this, our order of magnitude number would have to be  
1000 subscribers per IPv4 address = a /22 per million users.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 05:58:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F10DA3A6AF2;
	Tue,  5 Aug 2008 05:58:50 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D441A3A695B;
	Tue,  5 Aug 2008 05:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.669
X-Spam-Level: 
X-Spam-Status: No, score=-1.669 tagged_above=-999 required=5 tests=[AWL=0.930, 
	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 tFm7LMwT3LxR; Tue,  5 Aug 2008 05:58:46 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194])
	by core3.amsl.com (Postfix) with ESMTP id 7393B3A6B08;
	Tue,  5 Aug 2008 05:58:46 -0700 (PDT)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis)
	id 0MKpCa-1KQM7y3W1p-0004R1; Tue, 05 Aug 2008 08:59:09 -0400
Message-ID: <0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
	"Brian E Carpenter" <brian.e.carpenter@gmail.com>
References: <4897AFC0.9080007@gmail.com>
	<475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
Date: Tue, 5 Aug 2008 07:59:32 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Provags-ID: V01U2FsdGVkX19oHoICtskcDeafbGycTRH2OfDV69MJdsPRjXp
	ej4kyoPuuAR6hCzLPZlUxAhXTmCi4koRkclB1Aomwdd/yeI9B9
	oOD6VwPYQFoVqm5FaYcDO7e5PKbLRN9wFj4mzMnDKs=
Cc: int-area@ietf.org, Richard Nelson <richardn@cs.waikato.ac.nz>,
	Shane Alcock <salcock@cs.waikato.ac.nz>, behave@ietf.org
Subject: Re: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Agreeing with Iljitch's math here, but ...

>> In case people aren't already aware of it, I think the work at the
>> second URL below is very interesting in discussing the possible
>> implications of CGN, and in particular the number of outbound and
>> inbound ports needed per active host.
>
> Hm, it looks like the high water marks for TCP and UDP sessions per 
> subscriber (including non-active subscribers) is around 20 and 40.
>
> For our purposes we can probably assume that the UDP is lower than TCP 
> because UDP in this is very likely mostly DNS which shouldn't have to  go 
> through a NAT64.
>
> So that means a single IPv4 address can support about 3000 subscribers.

... the "planning for 500 connections per user" reference in the plenary 
presentation last week was way higher than I've heard previously, but the 
working number from the P2PI workshop in May was about 80 for BitTorrent, 
wasn't it? So we're already looking at a factor-of-two reduction in what we 
can support on one IPv4 address, before someone comes up with an even cuter 
connection-use strategy...

:-(

Spencer 


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 06:08:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E2FEF3A6A40;
	Tue,  5 Aug 2008 06:08:17 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E713A3A6A43;
	Tue,  5 Aug 2008 06:08:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level: 
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.030, 
	BAYES_00=-2.599, NO_RELAYS=-0.001]
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 Zv3uXw5G2Ubu; Tue,  5 Aug 2008 06:08:15 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id B06A73A691C;
	Tue,  5 Aug 2008 06:08:14 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m75D8DFo048052
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 5 Aug 2008 15:08:13 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
In-Reply-To: <0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
X-Priority: 3
References: <4897AFC0.9080007@gmail.com>
	<475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
	<0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
Message-Id: <54514B15-BC02-495D-903C-8235A6E6C5A7@muada.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 5 Aug 2008 15:08:35 +0200
X-Mailer: Apple Mail (2.926)
Cc: int-area@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>,
	Richard Nelson <richardn@cs.waikato.ac.nz>, behave@ietf.org
Subject: Re: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 5 aug 2008, at 14:59, Spencer Dawkins wrote:

>> So that means a single IPv4 address can support about 3000  
>> subscribers.

> ... the "planning for 500 connections per user" reference in the  
> plenary presentation last week was way higher than I've heard  
> previously, but the working number from the P2PI workshop in May was  
> about 80 for BitTorrent, wasn't it? So we're already looking at a  
> factor-of-two reduction in what we can support on one IPv4 address,  
> before someone comes up with an even cuter connection-use strategy...

> :-(

The problem is that today, BitTorrent is a very bad citizen when it  
comes to port number use: it uses many connections, and it keeps them  
open for a long time.

I would assume that a "carrier grade NAT" would implement per-user  
port number limits. Hopefully these will be such that BitTorrent etc  
can still run at night when other users don't need the ports.

But the real solution would be update the BitTorrent implementations  
so that they use a single source port, or at least a very small number  
of source ports, which has two benefits: it uses up fewer ports and  
it's now possible to use ICE to compensate for the loss of UPnP and  
NAT-PMP.

So the future doesn't look too bleak (and that's not even including  
the ability to use native IPv6!) but the road getting there could be a  
bit bumpy.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 06:25:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA7F13A6984;
	Tue,  5 Aug 2008 06:25:58 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 88FCF3A6892;
	Tue,  5 Aug 2008 06:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.283
X-Spam-Level: 
X-Spam-Status: No, score=-6.283 tagged_above=-999 required=5 tests=[AWL=0.016, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 pehidAwJKjZ0; Tue,  5 Aug 2008 06:25:56 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id B61253A67CC;
	Tue,  5 Aug 2008 06:25:56 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m75DQDcN017179; Tue, 5 Aug 2008 08:26:19 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 5 Aug 2008 16:26:19 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 5 Aug 2008 16:26:08 +0300
Received: from esdhcp04041.research.nokia.com ([172.21.40.41]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 5 Aug 2008 16:26:07 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org
Date: Tue, 5 Aug 2008 16:26:12 +0300
User-Agent: KMail/1.9.9
References: <4897AFC0.9080007@gmail.com>
	<0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
	<54514B15-BC02-495D-903C-8235A6E6C5A7@muada.com>
In-Reply-To: <54514B15-BC02-495D-903C-8235A6E6C5A7@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808051626.13242.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 Aug 2008 13:26:07.0563 (UTC)
	FILETIME=[D16AE9B0:01C8F6FE]
X-Nokia-AV: Clean
Cc: Richard Nelson <richardn@cs.waikato.ac.nz>, int-area@ietf.org,
	Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Tuesday 05 August 2008 16:08:35 ext Iljitsch van Beijnum, you wrote:
> But the real solution would be update the BitTorrent implementations
> so that they use a single source port, or at least a very small number
> of source ports, which has two benefits: it uses up fewer ports and
> it's now possible to use ICE to compensate for the loss of UPnP and
> NAT-PMP.

Except that ICE does not really support anything except UDP at this stage. =

BitTorrent, as a bulk transfer protocol, requires TCP. Also BitTorrent =

requires inbound connections to work on a significant proportion of nodes, =

which requires UPnP, NAT-PMP, a public IPv4 address, or, if the user is =

knowledgeable, static port forwarding.

For real-time traffic (such as VoIP), ICE is great, and we really need ISP =

NATs to support it. However, when it comes to peer-to-peer bulk transfer, I =

suspect a "carrier-grade NAT-PMP" will be more practical than "TCP-grade =

ICE".

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 06:28:20 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AA323A6984;
	Tue,  5 Aug 2008 06:28:20 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD8CB3A6984;
	Tue,  5 Aug 2008 06:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.284
X-Spam-Level: 
X-Spam-Status: No, score=-6.284 tagged_above=-999 required=5 tests=[AWL=0.015, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 5RvSfizSb9Bv; Tue,  5 Aug 2008 06:28:19 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 96AB73A67CC;
	Tue,  5 Aug 2008 06:28:18 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m75DSeSS011958; Tue, 5 Aug 2008 16:28:41 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 5 Aug 2008 16:28:25 +0300
Received: from esdhcp04041.research.nokia.com ([172.21.40.41]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 5 Aug 2008 16:28:24 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: int-area@ietf.org
Date: Tue, 5 Aug 2008 16:28:29 +0300
User-Agent: KMail/1.9.9
References: <4897AFC0.9080007@gmail.com>
	<475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
In-Reply-To: <475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808051628.29921.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 Aug 2008 13:28:24.0451 (UTC)
	FILETIME=[23025D30:01C8F6FF]
X-Nokia-AV: Clean
Cc: behave@ietf.org, Richard Nelson <richardn@cs.waikato.ac.nz>,
	Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Tuesday 05 August 2008 12:40:17 ext Iljitsch van Beijnum, you wrote:
> For our purposes we can probably assume that the UDP is lower than TCP
> because UDP in this is very likely mostly DNS which shouldn't have to
> go through a NAT64.

Real-time traffic, including online games, VoIP, videoconferencing, relies =

heavily on UDP, if only to avoid TCP head-of-line blocking.

If NAT vendors had not assumed that DNS was the only usage of UDP, we would =

probably have overall much better NAT in the real-world today. Please do no=
t =

make the same mistake.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 06:47:00 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5F8D28C26D;
	Tue,  5 Aug 2008 06:47:00 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C3C128C1C8;
	Tue,  5 Aug 2008 06:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.421
X-Spam-Level: 
X-Spam-Status: No, score=-2.421 tagged_above=-999 required=5
	tests=[AWL=-0.121, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	NO_RELAYS=-0.001]
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 BN2lNr+HPP3l; Tue,  5 Aug 2008 06:46:58 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 39D9D28C25C;
	Tue,  5 Aug 2008 06:46:51 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m75DksG1049723
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 5 Aug 2008 15:46:54 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <ACBC7F2E-E953-4A43-A08E-5984F684E825@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200808051626.13242.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 5 Aug 2008 15:47:15 +0200
References: <4897AFC0.9080007@gmail.com>
	<0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
	<54514B15-BC02-495D-903C-8235A6E6C5A7@muada.com>
	<200808051626.13242.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.926)
Cc: int-area@ietf.org, Richard Nelson <richardn@cs.waikato.ac.nz>,
	behave@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 5 aug 2008, at 15:26, R=E9mi Denis-Courmont wrote:

> Except that ICE does not really support anything except UDP at this  =

> stage.

What's the difficulty with TCP? If I understand things correctly, once  =

you use a certain port as a source port number on the public side, a  =

behave-compliant NAT will forward incoming sessions towards that port  =

number to you. So the only thing the application has to do is figure  =

out what the address/port is that others see and not release the port  =

number and it's in business.

So BitTorrent doesn't really need ICE, just STUN functionality for TCP.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 06:49:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4913D28C12D;
	Tue,  5 Aug 2008 06:49:29 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D35F3A679C;
	Tue,  5 Aug 2008 06:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Level: 
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5
	tests=[AWL=-0.118, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	NO_RELAYS=-0.001]
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 7Bp4Jb3IqZa8; Tue,  5 Aug 2008 06:49:24 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 54B5C28C1B7;
	Tue,  5 Aug 2008 06:49:24 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m75DnP8j049815
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 5 Aug 2008 15:49:25 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <C92872C7-8CE5-4C29-A6A6-CF84FDA94FE8@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200808051628.29921.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 5 Aug 2008 15:49:47 +0200
References: <4897AFC0.9080007@gmail.com>
	<475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
	<200808051628.29921.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.926)
Cc: Richard Nelson <richardn@cs.waikato.ac.nz>,
	Shane Alcock <salcock@cs.waikato.ac.nz>, int-area@ietf.org, behave@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 5 aug 2008, at 15:28, R=E9mi Denis-Courmont wrote:

>> For our purposes we can probably assume that the UDP is lower than  =

>> TCP
>> because UDP in this is very likely mostly DNS which shouldn't have to
>> go through a NAT64.

> Real-time traffic, including online games, VoIP, videoconferencing,  =

> relies
> heavily on UDP, if only to avoid TCP head-of-line blocking.

Huh? Head of line blocking?

> If NAT vendors had not assumed that DNS was the only usage of UDP,  =

> we would
> probably have overall much better NAT in the real-world today.  =

> Please do not
> make the same mistake.

Obviously UDP is used for many things, but everything that you mention  =

keeps a UDP "session" going for some time unless I'm very much  =

mistaken. DNS queries on the other hand use a different port for  =

pretty much every new packet.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 07:10:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7CE113A6CA4;
	Tue,  5 Aug 2008 07:10:30 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF2803A6C5B;
	Tue,  5 Aug 2008 07:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.285
X-Spam-Level: 
X-Spam-Status: No, score=-6.285 tagged_above=-999 required=5 tests=[AWL=0.014, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 eVDMVH8Xqr9h; Tue,  5 Aug 2008 07:10:28 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 47C3428C18E;
	Tue,  5 Aug 2008 07:09:31 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m75E9ZRj025382; Tue, 5 Aug 2008 17:09:41 +0300
Received: from vaebh103.NOE.Nokia.com ([10.160.244.24]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 5 Aug 2008 17:09:22 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 5 Aug 2008 17:09:21 +0300
Received: from esdhcp04041.research.nokia.com ([172.21.40.41]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 5 Aug 2008 17:09:20 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: "ext Iljitsch van Beijnum" <iljitsch@muada.com>
Date: Tue, 5 Aug 2008 17:09:25 +0300
User-Agent: KMail/1.9.9
References: <4897AFC0.9080007@gmail.com>
	<200808051626.13242.remi.denis-courmont@nokia.com>
	<ACBC7F2E-E953-4A43-A08E-5984F684E825@muada.com>
In-Reply-To: <ACBC7F2E-E953-4A43-A08E-5984F684E825@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808051709.26553.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 Aug 2008 14:09:20.0541 (UTC)
	FILETIME=[DAF3F4D0:01C8F704]
X-Nokia-AV: Clean
Cc: int-area@ietf.org, Richard Nelson <richardn@cs.waikato.ac.nz>,
	behave@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Tuesday 05 August 2008 16:47:15 ext Iljitsch van Beijnum, you wrote:
> What's the difficulty with TCP? If I understand things correctly, once
> you use a certain port as a source port number on the public side, a
> behave-compliant NAT will forward incoming sessions towards that port
> number to you. So the only thing the application has to do is figure
> out what the address/port is that others see and not release the port
> number and it's in business.

The passive side of the TCP connections can hardly be behind a NAT. So ther=
e =

is no way the NAT can know about it. That's why we have UPnP IGD and NAT-PM=
P.

So... One proposed work-around is for both sides to be simultaneously activ=
e. =

The TCP spec allows this, but:
1/ Most firewalls and many NATs do not support this.
   They reset the connection.
2/ Some OS's do not support it either.
3/ When the OS supports it, it needs a cumbersome socket API hack involving=
 a =

listening socket and an connecting socket on the same port.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 07:41:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A44403A6B86;
	Tue,  5 Aug 2008 07:41:52 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 366363A684A;
	Tue,  5 Aug 2008 07:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level: 
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5
	tests=[AWL=-0.114, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	NO_RELAYS=-0.001]
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 C6cb9ROPMdPK; Tue,  5 Aug 2008 07:41:50 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 199733A68EA;
	Tue,  5 Aug 2008 07:41:49 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m75EfqQW051678
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 5 Aug 2008 16:41:53 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <B8790CBE-82AE-4729-884A-360C4F648B07@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200808051709.26553.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 5 Aug 2008 16:42:14 +0200
References: <4897AFC0.9080007@gmail.com>
	<200808051626.13242.remi.denis-courmont@nokia.com>
	<ACBC7F2E-E953-4A43-A08E-5984F684E825@muada.com>
	<200808051709.26553.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.926)
Cc: int-area@ietf.org, Richard Nelson <richardn@cs.waikato.ac.nz>,
	behave@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 5 aug 2008, at 16:09, R=E9mi Denis-Courmont wrote:

>> What's the difficulty with TCP? If I understand things correctly,  =

>> once
>> you use a certain port as a source port number on the public side, a
>> behave-compliant NAT will forward incoming sessions towards that port
>> number to you. So the only thing the application has to do is figure
>> out what the address/port is that others see and not release the port
>> number and it's in business.

> The passive side of the TCP connections can hardly be behind a NAT.

Isn't that the whole point of endpoint independent NATing?

I first open a session with source port 10 and destination address X.  =

The NAT rewrites the source port into 93 and the source address into  =

Y. The server at X tells me values 93 and Y. I then start listening on  =

port 10 and tell others to contact me on Y port 93.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 07:58:10 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F87028C2B0;
	Tue,  5 Aug 2008 07:58:10 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 09C5F28C2A6;
	Tue,  5 Aug 2008 07:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.295
X-Spam-Level: 
X-Spam-Status: No, score=-6.295 tagged_above=-999 required=5
	tests=[AWL=-0.046, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	RCVD_IN_DNSWL_MED=-4]
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 xpC54LS83mjy; Tue,  5 Aug 2008 07:58:08 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id ECEBC28C296;
	Tue,  5 Aug 2008 07:58:07 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	EA11620191; Tue,  5 Aug 2008 16:58:37 +0200 (CEST)
X-AuditID: c1b4fb3e-ae999bb000004ec0-3f-48986a9d8333
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	D5D3F20169; Tue,  5 Aug 2008 16:58:37 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Aug 2008 16:58:37 +0200
Received: from [147.214.183.47] ([147.214.183.47]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Aug 2008 16:58:37 +0200
Message-ID: <48986A9D.3040408@ericsson.com>
Date: Tue, 05 Aug 2008 16:58:37 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <4897AFC0.9080007@gmail.com>	<200808051626.13242.remi.denis-courmont@nokia.com>	<ACBC7F2E-E953-4A43-A08E-5984F684E825@muada.com>	<200808051709.26553.remi.denis-courmont@nokia.com>
	<B8790CBE-82AE-4729-884A-360C4F648B07@muada.com>
In-Reply-To: <B8790CBE-82AE-4729-884A-360C4F648B07@muada.com>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 05 Aug 2008 14:58:37.0317 (UTC)
	FILETIME=[BD542B50:01C8F70B]
X-Brightmail-Tracker: AAAAAA==
Cc: int-area@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>,
	Richard Nelson <richardn@cs.waikato.ac.nz>, behave@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Iljitsch van Beijnum skrev:
> On 5 aug 2008, at 16:09, R=E9mi Denis-Courmont wrote:
> =

>>> What's the difficulty with TCP? If I understand things correctly, once
>>> you use a certain port as a source port number on the public side, a
>>> behave-compliant NAT will forward incoming sessions towards that port
>>> number to you. So the only thing the application has to do is figure
>>> out what the address/port is that others see and not release the port
>>> number and it's in business.
> =

>> The passive side of the TCP connections can hardly be behind a NAT.
> =

> Isn't that the whole point of endpoint independent NATing?

To allow for it yes, but there is also the filtering behavior. NATs =

doesn't allow traffic in unless you have sent to that address or even =

address and port.
> =

> I first open a session with source port 10 and destination address X. =

> The NAT rewrites the source port into 93 and the source address into Y. =

> The server at X tells me values 93 and Y. I then start listening on port =

> 10 and tell others to contact me on Y port 93.

Yes, then when someone is going to connect you need to be told by the =

rendevous server that a client at address Z and port 4042 wants to =

connect. Then you can send a TCP SYN to Z:4042 from your port 10. That =

way the NAT opens for traffic. At the same time the client send to Y:93. =

Now the NAT needs to understand that it actually should consider this a =

simultaneous open situation.

Unfortunately I have to agree with Remi, for TCP and carrier NAT you =

really like to have a whole punching protocol for listing sockets.

There are some NATs that makes semi-static bindings without filtering in =

the NAT that makes what you suggest working for certain ports. So one =

can also consider what the full implications are of NATs without =

filtering rules.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 08:22:10 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A71F28C21D;
	Tue,  5 Aug 2008 08:22:10 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99C6E3A6C1D;
	Tue,  5 Aug 2008 08:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.039, 
	BAYES_00=-2.599, NO_RELAYS=-0.001]
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 yEQnems59Czj; Tue,  5 Aug 2008 08:22:08 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 5C9D63A69A2;
	Tue,  5 Aug 2008 08:22:08 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m75FM5Ae054264
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 5 Aug 2008 17:22:06 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <C2941C62-B16A-4168-AE51-0F8E4BD2250F@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <48986A9D.3040408@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 5 Aug 2008 17:22:25 +0200
References: <4897AFC0.9080007@gmail.com>	<200808051626.13242.remi.denis-courmont@nokia.com>	<ACBC7F2E-E953-4A43-A08E-5984F684E825@muada.com>	<200808051709.26553.remi.denis-courmont@nokia.com>
	<B8790CBE-82AE-4729-884A-360C4F648B07@muada.com>
	<48986A9D.3040408@ericsson.com>
X-Mailer: Apple Mail (2.926)
Cc: Alain Durand <Alain_Durand@cable.comcast.com>,
	"behave@ietf.org WG" <behave@ietf.org>,
	"int-area@ietf.org Area" <int-area@ietf.org>
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 5 aug 2008, at 16:58, Magnus Westerlund wrote:

>>> The passive side of the TCP connections can hardly be behind a NAT.

>> Isn't that the whole point of endpoint independent NATing?

> To allow for it yes, but there is also the filtering behavior. NATs  
> doesn't allow traffic in unless you have sent to that address or  
> even address and port.

Right, because of the unfortunate notion that NAT provides security.

With NAT64 this isn't an issue because even if the NAT64 were to  
filter, incoming sessions over IPv6 would still be possible so a  
filtering by a NAT64 doesn't provide any security. So any filtering  
would have to be done on the CPE and/or the hosts in question.

For a dual stack light type of solution this is slightly different,  
but in this case I think it would also be more secure to have the  
encapsulating CPE provide filtering rather than the ISP NAT, if  
filtering is desired.

In the absense of filtering on the NAT incoming sessions the way I  
described in my previous message should work, right?

> Unfortunately I have to agree with Remi, for TCP and carrier NAT you  
> really like to have a whole punching protocol for listing sockets.

So which is it then?

If the endpoint independent behavior doesn't buy us incoming sessions,  
what's the use and why would we impair the NAT box scalability for it?
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug  5 23:21:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 809363A6A82;
	Tue,  5 Aug 2008 23:21:19 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C0EF3A6A64;
	Tue,  5 Aug 2008 23:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.285
X-Spam-Level: 
X-Spam-Status: No, score=-6.285 tagged_above=-999 required=5 tests=[AWL=0.014, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 0VOYeJal407r; Tue,  5 Aug 2008 23:21:17 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 0E4E33A68E5;
	Tue,  5 Aug 2008 23:21:16 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m766LZON017043; Wed, 6 Aug 2008 09:21:35 +0300
Received: from vaebh103.NOE.Nokia.com ([10.160.244.24]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 6 Aug 2008 09:21:34 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 6 Aug 2008 09:21:28 +0300
Received: from esdhcp04041.research.nokia.com ([172.21.40.41]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 6 Aug 2008 09:21:27 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: "ext Iljitsch van Beijnum" <iljitsch@muada.com>
Date: Wed, 6 Aug 2008 09:21:33 +0300
User-Agent: KMail/1.9.9
References: <4897AFC0.9080007@gmail.com>
	<200808051709.26553.remi.denis-courmont@nokia.com>
	<B8790CBE-82AE-4729-884A-360C4F648B07@muada.com>
In-Reply-To: <B8790CBE-82AE-4729-884A-360C4F648B07@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808060921.34226.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 06 Aug 2008 06:21:27.0424 (UTC)
	FILETIME=[A87C0000:01C8F78C]
X-Nokia-AV: Clean
Cc: int-area@ietf.org, Richard Nelson <richardn@cs.waikato.ac.nz>,
	behave@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Tuesday 05 August 2008 17:42:14 ext Iljitsch van Beijnum, you wrote:
> On 5 aug 2008, at 16:09, R=E9mi Denis-Courmont wrote:
> >> What's the difficulty with TCP? If I understand things correctly,
> >> once
> >> you use a certain port as a source port number on the public side, a
> >> behave-compliant NAT will forward incoming sessions towards that port
> >> number to you. So the only thing the application has to do is figure
> >> out what the address/port is that others see and not release the port
> >> number and it's in business.
> >
> > The passive side of the TCP connections can hardly be behind a NAT.
>
> Isn't that the whole point of endpoint independent NATing?

If you prefer it that way:
most NATs and just about all firewalls are not at all BEHAVE-TCP-compliant =

today.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug  6 13:46:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA51628C36E;
	Wed,  6 Aug 2008 13:46:06 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EDEDB28C1A6;
	Wed,  6 Aug 2008 13:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.301
X-Spam-Level: 
X-Spam-Status: No, score=0.301 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, MIME_8BIT_HEADER=0.3]
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 hE9Sw-VCa4Wq; Wed,  6 Aug 2008 13:46:04 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194])
	by core3.amsl.com (Postfix) with ESMTP id C515028C342;
	Wed,  6 Aug 2008 13:46:03 -0700 (PDT)
Received: from s73602 (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173])
	by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis)
	id 0MKp8S-1KQpsx3c4T-0005uz; Wed, 06 Aug 2008 16:45:38 -0400
Message-ID: <0d5d01c8f805$66c46110$6501a8c0@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
	=?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><200808051628.29921.remi.denis-courmont@nokia.com>
	<C92872C7-8CE5-4C29-A6A6-CF84FDA94FE8@muada.com>
Date: Wed, 6 Aug 2008 15:45:38 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Provags-ID: V01U2FsdGVkX1/Ng9M0BT0Pj4YGSPoDpElw6zVYig3ZejjtzWP
	siybI1GxmlCD4MaDShiqbihBnYYyzf8dtreKIWdx5yqQDDPHZ7
	F8X7J1pBh+1ef9STZ8vzC6BCnwWLR0tuXYYbbeSvCI=
Cc: int-area@ietf.org, behave@ietf.org,
	Richard Nelson <richardn@cs.waikato.ac.nz>,
	Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This got skipped over ... but since you asked ...

>> Real-time traffic, including online games, VoIP, videoconferencing, 
>> relies
>> heavily on UDP, if only to avoid TCP head-of-line blocking.

> Huh? Head of line blocking?

TCP provides a reliable, stream-oriented service - so if you drop a packet, 
none of the packets that follow the dropped packet can be delivered to the 
application until the dropped packet is retransmitted and received. So, the 
sequence number gap blocks all subsequent delivery until that happens.

Spencer 


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug  6 15:27:45 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3212E3A6A1F;
	Wed,  6 Aug 2008 15:27:45 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 23C1D3A69E7
	for <behave@core3.amsl.com>; Wed,  6 Aug 2008 15:27:44 -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=[AWL=0.000, 
	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 LJKtE9Hjw+G3 for <behave@core3.amsl.com>;
	Wed,  6 Aug 2008 15:27:43 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238])
	by core3.amsl.com (Postfix) with ESMTP id 57F863A682D
	for <behave@ietf.org>; Wed,  6 Aug 2008 15:27:43 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so115229rvf.49
	for <behave@ietf.org>; Wed, 06 Aug 2008 15:28:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=skd2ylf9V5JWCF6Ik6Ywim9oPB2InyCcwyM5OLK/Dnw=;
	b=K4L49nq2bxMMVrbQK6ZY8oVn1NZLdu3HLSbDih7NT/0KspPIIYP8+k04OESO73PHZ2
	WJci76bw4oDRc0iQqvjth2A1Tgm23B9JKHyRq1XU7gmsTNNwjCFGO2TEEuEqNhXCWsqW
	ZTXX8zNlLY1NwQXMGGFnZDb1utFQzuo/11dBg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=NtXVnxALqaV/XM9rce5oBdmeEUOKUj8vQ5J3/ofRjJGg8/L+M++zxWea8Cvlk4ECJu
	XHl3DFb6KpJrs2j9QfXMJaOkJXE/903No020XXxnYlcJaJrwweQRGQ2mwrsIKwPatHMV
	HF8hI21BA0KOdywJb+6l9GiEBpPDhYxS+GQpM=
Received: by 10.141.15.19 with SMTP id s19mr318155rvi.205.1218061696391;
	Wed, 06 Aug 2008 15:28:16 -0700 (PDT)
Received: from ?130.216.38.124? ( [130.216.38.124])
	by mx.google.com with ESMTPS id g31sm12402760rvb.2.2008.08.06.15.28.13
	(version=SSLv3 cipher=RC4-MD5); Wed, 06 Aug 2008 15:28:15 -0700 (PDT)
Message-ID: <489A2576.5060606@gmail.com>
Date: Thu, 07 Aug 2008 10:28:06 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Spencer Dawkins <spencer@wonderhamster.org>
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><200808051628.29921.remi.denis-courmont@nokia.com>	<C92872C7-8CE5-4C29-A6A6-CF84FDA94FE8@muada.com>
	<0d5d01c8f805$66c46110$6501a8c0@china.huawei.com>
In-Reply-To: <0d5d01c8f805$66c46110$6501a8c0@china.huawei.com>
Cc: behave@ietf.org, Richard Nelson <richardn@cs.waikato.ac.nz>,
	Shane Alcock <salcock@cs.waikato.ac.nz>,
	=?UTF-8?B?UsOpbWkgRGVuaXMt?=@core3.amsl.com, int-area@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 2008-08-07 08:45, Spencer Dawkins wrote:
> This got skipped over ... but since you asked ...
> 
>>> Real-time traffic, including online games, VoIP, videoconferencing,
>>> relies
>>> heavily on UDP, if only to avoid TCP head-of-line blocking.
> 
>> Huh? Head of line blocking?
> 
> TCP provides a reliable, stream-oriented service - so if you drop a
> packet, none of the packets that follow the dropped packet can be
> delivered to the application until the dropped packet is retransmitted
> and received. So, the sequence number gap blocks all subsequent delivery
> until that happens.

Which is the fundamental weirdness about using TCP to deliver media streams,
since codecs generally prefer to forget about a dropped packet ASAP and
just get on with the next packet.

    Brian
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug  6 21:09:22 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 404F83A6BF3;
	Wed,  6 Aug 2008 21:09:22 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B55CA3A69D2;
	Wed,  6 Aug 2008 21:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.537
X-Spam-Level: 
X-Spam-Status: No, score=-103.537 tagged_above=-999 required=5
	tests=[AWL=0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1,
	USER_IN_WHITELIST=-100]
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 v+eU4GHq0yYF; Wed,  6 Aug 2008 21:09:19 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7])
	by core3.amsl.com (Postfix) with ESMTP id AB9893A6B60;
	Wed,  6 Aug 2008 21:09:19 -0700 (PDT)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1])
	by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
	with ESMTP-TLS id 12389634; Thu, 07 Aug 2008 00:09:46 -0400
Message-Id: <4C77C132-5500-4716-AD99-8A71ACC7DFBB@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <489A2576.5060606@gmail.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 7 Aug 2008 00:09:45 -0400
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><200808051628.29921.remi.denis-courmont@nokia.com>	<C92872C7-8CE5-4C29-A6A6-CF84FDA94FE8@muada.com>
	<0d5d01c8f805$66c46110$6501a8c0@china.huawei.com>
	<489A2576.5060606@gmail.com>
X-Mailer: Apple Mail (2.926)
Cc: Richard Nelson <richardn@cs.waikato.ac.nz>, int-area@ietf.org,
	behave@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] [Int-area]    Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dear Brian;

On Aug 6, 2008, at 6:28 PM, Brian E Carpenter wrote:

> On 2008-08-07 08:45, Spencer Dawkins wrote:
>> This got skipped over ... but since you asked ...
>>
>>>> Real-time traffic, including online games, VoIP, videoconferencing,
>>>> relies
>>>> heavily on UDP, if only to avoid TCP head-of-line blocking.
>>
>>> Huh? Head of line blocking?
>>
>> TCP provides a reliable, stream-oriented service - so if you drop a
>> packet, none of the packets that follow the dropped packet can be
>> delivered to the application until the dropped packet is  
>> retransmitted
>> and received. So, the sequence number gap blocks all subsequent  
>> delivery
>> until that happens.
>
> Which is the fundamental weirdness about using TCP to deliver media  
> streams,
> since codecs generally prefer to forget about a dropped packet ASAP  
> and
> just get on with the next packet.

Streaming media (as opposed to video conferencing or VOIP)
typically use large (multi-second) buffers, so they can use even  
fairly late packets.
The tcp streaming generally cannot recover from a timeout of the TCP  
session, though.

Regards
Marshall

>
>
> Brian
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug  7 00:41:45 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 684983A6A6C;
	Thu,  7 Aug 2008 00:41:45 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B59C63A6A14;
	Thu,  7 Aug 2008 00:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.052, 
	BAYES_00=-2.599, NO_RELAYS=-0.001]
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 zO8MfAA7KvVo; Thu,  7 Aug 2008 00:41:43 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 79D6F3A6A13;
	Thu,  7 Aug 2008 00:41:42 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m777fhQE011378
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 7 Aug 2008 09:41:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
In-Reply-To: <0d5d01c8f805$66c46110$6501a8c0@china.huawei.com>
X-Priority: 3
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><200808051628.29921.remi.denis-courmont@nokia.com>
	<C92872C7-8CE5-4C29-A6A6-CF84FDA94FE8@muada.com>
	<0d5d01c8f805$66c46110$6501a8c0@china.huawei.com>
Message-Id: <4AEBE84C-9035-4E22-BFDF-503B2AD2B88A@muada.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 7 Aug 2008 09:42:05 +0200
X-Mailer: Apple Mail (2.926)
Cc: behave@ietf.org, Richard Nelson <richardn@cs.waikato.ac.nz>,
	int-area@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 6 aug 2008, at 22:45, Spencer Dawkins wrote:

>>> Real-time traffic, including online games, VoIP,  
>>> videoconferencing, relies
>>> heavily on UDP, if only to avoid TCP head-of-line blocking.

>> Huh? Head of line blocking?

> TCP provides a reliable, stream-oriented service - so if you drop a  
> packet, none of the packets that follow the dropped packet can be  
> delivered to the application until the dropped packet is  
> retransmitted and received. So, the sequence number gap blocks all  
> subsequent delivery until that happens.

Oh, right. It read like TCP packets would be stuck in router  
buffers... I wasn't aware that the term head of line blocking was also  
used in an end-to-end context.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug  7 10:41:27 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5EC553A68FF;
	Thu,  7 Aug 2008 10:41:27 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5C463A68FF
	for <behave@core3.amsl.com>; Thu,  7 Aug 2008 10:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.554
X-Spam-Level: 
X-Spam-Status: No, score=-6.554 tagged_above=-999 required=5 tests=[AWL=0.045, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 P39HHWO4Z13m for <behave@core3.amsl.com>;
	Thu,  7 Aug 2008 10:41:25 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 808F03A67B3
	for <behave@ietf.org>; Thu,  7 Aug 2008 10:41:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,321,1215388800"; d="scan'208";a="93431711"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 07 Aug 2008 17:41:54 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m77HfsiC030984; 
	Thu, 7 Aug 2008 10:41:54 -0700
Received: from dwingwxp01 (sjc-vpn5-1491.cisco.com [10.21.93.211])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m77Hfnh9020081;
	Thu, 7 Aug 2008 17:41:50 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
Date: Thu, 7 Aug 2008 10:41:47 -0700
Message-ID: <059001c8f8b4$e04e2ac0$d35d150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acj4Yp33PZtGr5f4QUW6TZ68gCZFAAAAQz5QABRA6vA=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1800; t=1218130914;
	x=1218994914; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20FW=3A=20translator=20friendly=20DNS=20Proxy
	|Sender:=20; bh=FxKwlOtKOmH5JZ/sOzqJ+wTUVCqhb9XMG2y0iWbwnvM=;
	b=GuVv1K1JKaLpGianG6Pg6pBCzHPc4ncJzXhGcsUlPOYraNzytEjpbgdKxo
	iJuADPskKXu0ce21/8FWBfrMsI0aIh4IBgEg6E8pEwGO9xMIEopnVklt04FE
	wpzpn9J75Z;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: Masahito.Endou@jp.yokogawa.com, h.miyata@jp.yokogawa.com
Subject: [BEHAVE] FW: translator friendly DNS Proxy
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This draft is probably of interest to Behave.

-d


-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On Behalf Of
Masahito.Endou@jp.yokogawa.com
Sent: Thursday, August 07, 2008 1:35 AM
To: v6ops@ops.ietf.org
Subject: translator friendly DNS Proxy

Hi, all

I submitted this document.

In this document, I proposed DNS proxy that is separated from NAT-PT.
This document describes about relationship DNS proxy and sNATPT[1].
I think that this DNS proxy can collabolate with other translation
technologies.

I know that this working group isn't appropriate to discuss such kind items,
but I informed this document bacause many people that are interested in
subscribed this mailing list.
And, if there is more suitable working group to discuss it, please tell me
that.

[1] sNATPT: Miyata, H., "Simplified Network Address Translation - Protocol
Translation"
                   draft-miyata-v6ops-snatpt-00

Thanks your comments.
Best Regards,

--------------------------
A new version of I-D, draft-endo-v6ops-dnsproxy-00.txt has been successfuly
submitted by Masahito Endo and posted to the IETF repository.

Filename:        draft-endo-v6ops-dnsproxy
Revision:        00
Title:           Translator Friendly DNS Proxy
Creation_date:   2008-08-07
WG ID:           Independent Submission
Number_of_pages: 24

Abstract:
This document describes the DNS Proxy that is separated from NAT-PT [RFC2766].
NAT-PT was designed to work with DNS Application Level Gateway.  However
[RFC4966] pointed out DNS related issues, and [RFC2766] was changed to
historical state.  This document attempts to DNS Proxy specification, removing
dependency on NAT-PT as well as resolving problems pointed in [RFC4966].

// masaxmasa

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug  7 10:42:27 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D95243A67F2;
	Thu,  7 Aug 2008 10:42:27 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1747D3A67F2
	for <behave@core3.amsl.com>; Thu,  7 Aug 2008 10:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.555
X-Spam-Level: 
X-Spam-Status: No, score=-6.555 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 wOHBxUd5pNNH for <behave@core3.amsl.com>;
	Thu,  7 Aug 2008 10:42:25 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 289D23A67B3
	for <behave@ietf.org>; Thu,  7 Aug 2008 10:42:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,321,1215388800"; d="scan'208";a="137077234"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 07 Aug 2008 17:42:44 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m77HgiZf010407; 
	Thu, 7 Aug 2008 10:42:44 -0700
Received: from dwingwxp01 (sjc-vpn5-1491.cisco.com [10.21.93.211])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m77HgcGd020774;
	Thu, 7 Aug 2008 17:42:43 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Masahito.Endou@jp.yokogawa.com>, <v6ops@ops.ietf.org>
References: <B76F972AA81DDB4F8E4BA80DEDE43983D32CACB327@EXMAIL03.jp.ykgw.net>
Date: Thu, 7 Aug 2008 10:42:34 -0700
Message-ID: <05bc01c8f8b4$ff1299f0$d35d150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acj4Yp33PZtGr5f4QUW6TZ68gCZFAAAAQz5QABQoFpA=
In-Reply-To: <B76F972AA81DDB4F8E4BA80DEDE43983D32CACB327@EXMAIL03.jp.ykgw.net>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2301; t=1218130964;
	x=1218994964; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20translator=20friendly=20DNS=20Proxy
	|Sender:=20; bh=25922yY4oufUiUUGTZrnsxIM4AjQIjASJI0JMq8uCys=;
	b=QPqeEcb6j62uGFzjRhGrD4l2WHyWiDx3LetAgUTwsSY0M4+6V3m0D/MLWE
	uxYHAW1EU+ySYaMNYwxiPgKS5n3qG+UdZo+KoQx/TGxiShvMa7LR+a8G5T35
	85PBmdxsoz;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: h.miyata@jp.yokogawa.com, 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] translator friendly DNS Proxy
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> -----Original Message-----
> From: owner-v6ops@ops.ietf.org 
> [mailto:owner-v6ops@ops.ietf.org] On Behalf Of 
> Masahito.Endou@jp.yokogawa.com
> Sent: Thursday, August 07, 2008 1:35 AM
> To: v6ops@ops.ietf.org
> Subject: translator friendly DNS Proxy
> 
> Hi, all
> 
> I submitted this document.
> 
> In this document, I proposed DNS proxy that is separated from NAT-PT.
> This document describes about relationship DNS proxy and sNATPT[1].
> I think that this DNS proxy can collabolate with other 
> translation technologies.
> 
> I know that this working group isn't appropriate to discuss 
> such kind items,
> but I informed this document bacause many people that are 
> interested in subscribed this mailing list.
> And, if there is more suitable working group to discuss it, 
> please tell me that.

The Behave working group would be best,
<http://www.ietf.org/html.charters/behave-charter.html>.  I just forwarded
your announcement to the Behave mailing list.

> [1] sNATPT: Miyata, H., "Simplified Network Address 
> Translation - Protocol Translation"
>                    draft-miyata-v6ops-snatpt-00

I read your draft, and it seems like the Translator Interface
is the key -- it is the interface between the DNS Proxy (which
synthesizes AAAA records) you describe, and the NAT-PT itself
(which NATs between v6 and v4).  

Do I understand correctly?

-d


> Thanks your comments.
> Best Regards,
> 
> --------------------------
> A new version of I-D, draft-endo-v6ops-dnsproxy-00.txt has 
> been successfuly submitted by Masahito Endo and posted to the 
> IETF repository.
> 
> Filename:        draft-endo-v6ops-dnsproxy
> Revision:        00
> Title:           Translator Friendly DNS Proxy
> Creation_date:   2008-08-07
> WG ID:           Independent Submission
> Number_of_pages: 24
> 
> Abstract:
> This document describes the DNS Proxy that is separated from 
> NAT-PT [RFC2766].  NAT-PT was designed to work with DNS 
> Application Level Gateway.  However [RFC4966] pointed out DNS 
> related issues, and [RFC2766] was changed to historical 
> state.  This document attempts to DNS Proxy specification, 
> removing dependency on NAT-PT as well as resolving problems 
> pointed in [RFC4966].
> 
> // masaxmasa
> 

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug  7 18:24:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5B163A6C65;
	Thu,  7 Aug 2008 18:24:29 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 49C3B3A6C65;
	Thu,  7 Aug 2008 18:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 cF5rre2vt1Bz; Thu,  7 Aug 2008 18:24:27 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 5B68B3A682A;
	Thu,  7 Aug 2008 18:24:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,323,1215388800"; d="scan'208";a="137262493"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 08 Aug 2008 01:24:25 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m781OPL3022254; 
	Thu, 7 Aug 2008 18:24:25 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m781OOP1018076;
	Fri, 8 Aug 2008 01:24:24 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "Behave WG" <behave@ietf.org>
Date: Thu, 7 Aug 2008 18:24:22 -0700
Message-ID: <214901c8f8f5$7d5ea610$d35d150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acj49Xzun/wVC6D6QQCAcBe4RCQB+A==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=261; t=1218158665; x=1219022665;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20WGLC=3A=20draft-ietf-behave-dccp-01 |Sender:=20;
	bh=fUNbnAHuDQ53ZkUDS4vxirRk7kyqxm8hTcaTO4Azuqk=;
	b=nVBuTqBdqKQSwTGBIeoK3z3Q42tpa8wToGkZ9apf3sBOAo7wcNPZW6ccYp
	qG92KS2m/UPUemoNk08bChrznMlZEmM583koiisBe6fDni8XHlI1vS81kgJ1
	PJFHpkEWSe;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: dccp@ietf.org, rem@videolan.org
Subject: [BEHAVE] WGLC: draft-ietf-behave-dccp-01
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Behave is commencing a 2-week WGLC for "Network Address Translation (NAT)
Behavioral Requirements for DCCP",
<http://tools.ietf.org/html/draft-ietf-behave-dccp-01>.  The WGLC will end on
August 21.

Please send comments to the author and to Behave.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug  7 18:26:31 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F32F3A6C68;
	Thu,  7 Aug 2008 18:26:31 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 391123A682A
	for <behave@core3.amsl.com>; Thu,  7 Aug 2008 18:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 MSWf2s2jdOsR for <behave@core3.amsl.com>;
	Thu,  7 Aug 2008 18:26:30 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 75E5628C140
	for <behave@ietf.org>; Thu,  7 Aug 2008 18:26:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,323,1215388800"; d="scan'208";a="93567292"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 08 Aug 2008 01:26:30 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m781QUqT013295; 
	Thu, 7 Aug 2008 18:26:30 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m781QTq4027503;
	Fri, 8 Aug 2008 01:26:29 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "Behave WG" <behave@ietf.org>
Date: Thu, 7 Aug 2008 18:26:29 -0700
Message-ID: <214a01c8f8f5$c8d16060$d35d150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acj49chXEUhnIsNDRWmJ5MkbBUEVng==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=257; t=1218158790; x=1219022790;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=202nd=20WGLC=20draft-ietf-behave-nat-behavior-dis
	covery-04 |Sender:=20;
	bh=G8fjRNFKr08Z/TzTjeqKhPnLVY72vrpmTvkBQGJijzM=;
	b=axPvXyFeunvmQ6nmOvdr0xbaUssFqbTNnVVnGA1uALGO6FT5QaUvVyEssk
	UP0jlZ8g4xH/AVbnGcZPzK9M4vrhseU2n9/GTjbF/Y5k+SfdCJXPiZh4jZ2F
	Z2vtyjhvQS;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [BEHAVE] 2nd WGLC draft-ietf-behave-nat-behavior-discovery-04
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I'd like to do a quick one week 2nd WGLC on "NAT Behavior Discovery Using
STUN",
<http://tools.ietf.org/html/draft-ietf-behave-nat-behavior-discovery-04>.
This will end on August 14th.  

Please send comments to the authors (CC'd) and the list.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug  7 18:30:20 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC7393A68C0;
	Thu,  7 Aug 2008 18:30:20 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8631D3A68C0
	for <behave@core3.amsl.com>; Thu,  7 Aug 2008 18:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 rLboCvhGyZVO for <behave@core3.amsl.com>;
	Thu,  7 Aug 2008 18:30:18 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id BE5CB3A682A
	for <behave@ietf.org>; Thu,  7 Aug 2008 18:30:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,323,1215388800"; d="scan'208";a="63049630"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 08 Aug 2008 01:30:18 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m781UIuf026957; 
	Thu, 7 Aug 2008 18:30:18 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m781UHmN021042;
	Fri, 8 Aug 2008 01:30:17 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "Behave WG" <behave@ietf.org>
Date: Thu, 7 Aug 2008 18:30:17 -0700
Message-ID: <214e01c8f8f6$50d10ce0$d35d150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acj49lAUv7LVWxGKTK6zL1NpuCdhJA==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=460; t=1218159018; x=1219023018;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20adopt=20draft-stewart-behave-sctpnat-04?
	|Sender:=20; bh=pimtaE5qs3U3jVfI4aYpU5ajNjap7UnPr9lDT3l/jz8=;
	b=UYKpvOGUj6AhDTeNhGYLVMmB2+/UQQxqfusUvjp42oulRsZa3lUVDr5uko
	afxLHNqIabk4So0YL6j26P4s9YYTWJGsYyzD+S9ZtL6TLPvEJXat6F74QTRp
	U37QrVlW47;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: i.ruengeler@fh-muenster.de, 'Michael Tuexen' <tuexen@fh-muenster.de>
Subject: [BEHAVE] adopt draft-stewart-behave-sctpnat-04?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

The authors of "Stream Control Transmission Protocol (SCTP) Network Address
Translation" have asked their document
<http://tools.ietf.org/html/draft-stewart-behave-sctpnat-04> to be adopted by
Behave to meet the WG milestone for NATting SCTP.  As a reminder, their
presentation from the Dublin meeting is at
<http://www.ietf.org/proceedings/08jul/slides/behave-2.pdf>.

Please send comments on adopting this document to the Behave list.

Thanks,
-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug  7 19:15:01 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AECC428C1DA;
	Thu,  7 Aug 2008 19:15:01 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DFD4528C1A5
	for <behave@core3.amsl.com>; Thu,  7 Aug 2008 19:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.085
X-Spam-Level: ***
X-Spam-Status: No, score=3.085 tagged_above=-999 required=5 tests=[AWL=2.181, 
	BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,
	RELAY_IS_203=0.994]
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 G3u9uzQzcuKy for <behave@core3.amsl.com>;
	Thu,  7 Aug 2008 19:15:00 -0700 (PDT)
Received: from zns001-0m9003.yokogawa.co.jp (zns001-0m9003.yokogawa.co.jp
	[203.174.79.161])
	by core3.amsl.com (Postfix) with ESMTP id CE39028C1DA
	for <behave@ietf.org>; Thu,  7 Aug 2008 19:14:59 -0700 (PDT)
Received: from zns001-0m9003.yokogawa.co.jp (localhost [127.0.0.1])
	by zns001-0m9003.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	m782EvaB001628; Fri, 8 Aug 2008 11:14:57 +0900 (JST)
Received: from zex001-0m9026.jp.ykgw.net (zex001-0m9026.jp.ykgw.net
	[10.0.11.45])
	by zns001-0m9003.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	m782Ev39001624; Fri, 8 Aug 2008 11:14:57 +0900 (JST)
Received: from EXMAIL01.jp.ykgw.net ([10.0.11.27]) by
	zex001-0m9026.jp.ykgw.net ([10.0.11.45]) with mapi;
	Fri, 8 Aug 2008 11:14:57 +0900
From: <H.Miyata@jp.yokogawa.com>
To: <dwing@cisco.com>, <behave@ietf.org>
Date: Fri, 8 Aug 2008 11:14:56 +0900
Thread-Topic: translator friendly DNS Proxy
Thread-Index: Acj4Yp33PZtGr5f4QUW6TZ68gCZFAAAAQz5QABRA6vAAEZDNAA==
Message-ID: <ADE3B17A83704A4592D9C37C8E21CA6E01071F2FAD4C@EXMAIL01.jp.ykgw.net>
In-Reply-To: <059001c8f8b4$e04e2ac0$d35d150a@cisco.com>
Accept-Language: ja-JP
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: ja-JP
MIME-Version: 1.0
Cc: Masahito.Endou@jp.yokogawa.com
Subject: Re: [BEHAVE] translator friendly DNS Proxy
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks Dan,

These two documents are described to resolve original NAT-PT specification
by separating translator and DNS proxy roll clearly.

        draft-miyata-v6ops-snatpt
        draft-endo-v6ops-dnsproxy

The relationship between above two functions looks like totd and TRT.
(Actually, the snapt works on IP layer)
Once we can make them simple, we can assemble each functions
to adopt any user's requirement.

Thanks for your comments!

------------------------------------
Hiroshi Miyata
Network & Software Development Dept.
Yokogawa Electric Corp.


-----Original Message-----
From: Dan Wing [mailto:dwing@cisco.com]
Sent: Friday, August 08, 2008 2:42 AM
To: 'Behave WG'
Cc: Endou, Masahito (Masahito.Endou@jp.yokogawa.com); Miyata, Hiroshi (H.Miyata@jp.yokogawa.com)
Subject: FW: translator friendly DNS Proxy

This draft is probably of interest to Behave.

-d


-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On Behalf Of Masahito.Endou@jp.yokogawa.com
Sent: Thursday, August 07, 2008 1:35 AM
To: v6ops@ops.ietf.org
Subject: translator friendly DNS Proxy

Hi, all

I submitted this document.

In this document, I proposed DNS proxy that is separated from NAT-PT.
This document describes about relationship DNS proxy and sNATPT[1].
I think that this DNS proxy can collabolate with other translation technologies.

I know that this working group isn't appropriate to discuss such kind items, but I informed this document bacause many people that are interested in subscribed this mailing list.
And, if there is more suitable working group to discuss it, please tell me that.

[1] sNATPT: Miyata, H., "Simplified Network Address Translation - Protocol Translation"
                   draft-miyata-v6ops-snatpt-00

Thanks your comments.
Best Regards,

--------------------------
A new version of I-D, draft-endo-v6ops-dnsproxy-00.txt has been successfuly submitted by Masahito Endo and posted to the IETF repository.

Filename:        draft-endo-v6ops-dnsproxy
Revision:        00
Title:           Translator Friendly DNS Proxy
Creation_date:   2008-08-07
WG ID:           Independent Submission
Number_of_pages: 24

Abstract:
This document describes the DNS Proxy that is separated from NAT-PT [RFC2766].
NAT-PT was designed to work with DNS Application Level Gateway.  However [RFC4966] pointed out DNS related issues, and [RFC2766] was changed to historical state.  This document attempts to DNS Proxy specification, removing dependency on NAT-PT as well as resolving problems pointed in [RFC4966].

// masaxmasa

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug  7 21:00:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2E8E3A6A3E;
	Thu,  7 Aug 2008 21:00:57 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 777DF3A689D
	for <behave@core3.amsl.com>; Thu,  7 Aug 2008 20:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.085
X-Spam-Level: ***
X-Spam-Status: No, score=3.085 tagged_above=-999 required=5 tests=[AWL=2.181, 
	BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,
	RELAY_IS_203=0.994]
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 NXYIZBuIwqId for <behave@core3.amsl.com>;
	Thu,  7 Aug 2008 20:02:55 -0700 (PDT)
Received: from zns001-0m9004.yokogawa.co.jp (zns001-0m9004.yokogawa.co.jp
	[203.174.79.162])
	by core3.amsl.com (Postfix) with ESMTP id 7357B3A685C
	for <behave@ietf.org>; Thu,  7 Aug 2008 20:02:55 -0700 (PDT)
Received: from zns001-0m9004.yokogawa.co.jp (localhost [127.0.0.1])
	by zns001-0m9004.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	m7832bse004678; Fri, 8 Aug 2008 12:02:37 +0900 (JST)
Received: from zex001-0m9027.jp.ykgw.net (zex001-0m9027.jp.ykgw.net
	[10.0.11.46])
	by zns001-0m9004.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	m7832SAt004577; Fri, 8 Aug 2008 12:02:28 +0900 (JST)
Received: from EXMAIL03.jp.ykgw.net ([10.0.11.29]) by
	zex001-0m9027.jp.ykgw.net ([10.0.11.46]) with mapi;
	Fri, 8 Aug 2008 12:02:28 +0900
From: <Masahito.Endou@jp.yokogawa.com>
To: <dwing@cisco.com>, <v6ops@ops.ietf.org>
Date: Fri, 8 Aug 2008 12:02:26 +0900
Thread-Topic: translator friendly DNS Proxy
Thread-Index: Acj4Yp33PZtGr5f4QUW6TZ68gCZFAAAAQz5QABQoFpAAEtHOMA==
Message-ID: <B76F972AA81DDB4F8E4BA80DEDE43983D32CACB34D@EXMAIL03.jp.ykgw.net>
In-Reply-To: <05bc01c8f8b4$ff1299f0$d35d150a@cisco.com>
Accept-Language: ja-JP
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: ja-JP
MIME-Version: 1.0
Cc: H.Miyata@jp.yokogawa.com, behave@ietf.org
Subject: Re: [BEHAVE] translator friendly DNS Proxy
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi, Dan

> > Hi, all
> >
> > I submitted this document.
> >
> > In this document, I proposed DNS proxy that is separated
> from NAT-PT.
> > This document describes about relationship DNS proxy and sNATPT[1].
> > I think that this DNS proxy can collabolate with other translation
> > technologies.
> >
> > I know that this working group isn't appropriate to discuss
> such kind
> > items, but I informed this document bacause many people that are
> > interested in subscribed this mailing list.
> > And, if there is more suitable working group to discuss it, please
> > tell me that.
>
> The Behave working group would be best,
> <http://www.ietf.org/html.charters/behave-charter.html>.  I
> just forwarded your announcement to the Behave mailing list.

Thanks for your information.
I just subscribed :)

> > [1] sNATPT: Miyata, H., "Simplified Network Address Translation -
> > Protocol Translation"
> >                    draft-miyata-v6ops-snatpt-00
>
> I read your draft, and it seems like the Translator Interface
> is the key -- it is the interface between the DNS Proxy
> (which synthesizes AAAA records) you describe, and the NAT-PT
> itself (which NATs between v6 and v4).
>
> Do I understand correctly?

Yes.
But actual key point is that the translator interface can separate DNS Proxy from NAT-PT.

If a translator has NAPT-PT rule for IPv6 to IPv4 translation, the translator interface is not required.
In this case, a translator maps a lot of IPv6 source addresses to one IPv4 source address,
so DNS Proxy doesn't need to care an IPv4 source address.

best regards,

// masaxmasa

> -d
>
>
> > Thanks your comments.
> > Best Regards,
> >
> > --------------------------
> > A new version of I-D, draft-endo-v6ops-dnsproxy-00.txt has been
> > successfuly submitted by Masahito Endo and posted to the IETF
> > repository.
> >
> > Filename:        draft-endo-v6ops-dnsproxy
> > Revision:        00
> > Title:           Translator Friendly DNS Proxy
> > Creation_date:   2008-08-07
> > WG ID:           Independent Submission
> > Number_of_pages: 24
> >
> > Abstract:
> > This document describes the DNS Proxy that is separated from NAT-PT
> > [RFC2766].  NAT-PT was designed to work with DNS Application Level
> > Gateway.  However [RFC4966] pointed out DNS related issues, and
> > [RFC2766] was changed to historical state.  This document
> attempts to
> > DNS Proxy specification, removing dependency on NAT-PT as well as
> > resolving problems pointed in [RFC4966].
> >
> > // masaxmasa
> >
>
>
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug  8 08:32:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 030203A684E;
	Fri,  8 Aug 2008 08:32:48 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3EDD3A6B04
	for <behave@core3.amsl.com>; Fri,  8 Aug 2008 00:20:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 mQmgS+1zO2FP for <behave@core3.amsl.com>;
	Fri,  8 Aug 2008 00:20:06 -0700 (PDT)
Received: from smtp-12.smtp.ucla.edu (smtp-12.smtp.ucla.edu [169.232.46.245])
	by core3.amsl.com (Postfix) with ESMTP id D95723A69D9
	for <behave@ietf.org>; Fri,  8 Aug 2008 00:20:06 -0700 (PDT)
Received: from mail.ucla.edu (mail.ucla.edu [169.232.47.146])
	by smtp-12.smtp.ucla.edu (8.14.3/8.14.3) with ESMTP id m787K4DT027496; 
	Fri, 8 Aug 2008 00:20:04 -0700
Received: from mug.lcdf.org (s2264-217.resnet.ucla.edu [164.67.64.217])
	(authenticated bits=0)
	by mail.ucla.edu (8.13.8/8.13.8) with ESMTP id m787K2RR004138
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 8 Aug 2008 00:20:03 -0700
Message-ID: <489BF319.3010103@cs.ucla.edu>
Date: Fri, 08 Aug 2008 00:17:45 -0700
From: Eddie Kohler <kohler@cs.ucla.edu>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>, rem@videolan.org
References: <214901c8f8f5$7d5ea610$d35d150a@cisco.com>
In-Reply-To: <214901c8f8f5$7d5ea610$d35d150a@cisco.com>
X-Probable-Spam: no
X-Spam-Hits: 0.654
X-Scanned-By: smtp.ucla.edu on 169.232.46.245
X-Mailman-Approved-At: Fri, 08 Aug 2008 08:32:46 -0700
Subject: Re: [BEHAVE] [dccp] WGLC: draft-ietf-behave-dccp-01
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Dear BEHAVE/Remi,

Thanks for producing this document!  There are two requirements that are more 
strict than I would expect.

(1) REQ-6: If a NAT includes ALGs, it MUST NOT affect DCCP.

(2) REQ-13: If a NAT translates a DCCP packet, it MUST NOT modify its
    DCCP service code value.

In both cases a related, less stringent requirement would be more reasonable IMHO.

(1) REQ-6b: NATs that include ALGs MUST NOT insert data packets into or remove 
data packets from DCCP streams.

RATIONALE:  "Therefore, modifying the payload of DCCP packets presents a 
significant additionnal challenge in maintaining sane DCCP sequence numbers, 
if the size of the payload were altered."  =>  DCCP sequence numbers are 
per-packet, not per-byte, so changing the size of a payload requires NO 
sequence number changes whatsoever.  Inserting or removing data packets DOES 
require sequence number changes, and should be avoided.

"Moreover, DCCP provides natural packet boundaries, whereby TCP provides a 
byte stream.  As such, changing the size of a DCCP packet may cause additional 
problems at the application layer."  =>  This is a little contradictory, since 
ALGs by definition "understand" the application layer and can prevent problems 
there.

RFC4340's Middlebox Considerations section says:

    Modifying DCCP Sequence Numbers and Acknowledgement Numbers is more
    tedious and dangerous than modifying TCP sequence numbers.  ...
    We therefore recommend that middleboxes not
    modify packet streams by adding or removing packets.

    Note that there is less need to modify DCCP's per-packet sequence
    numbers than to modify TCP's per-byte sequence numbers; for example,
    a middlebox can change the contents of a packet without changing its
    sequence number.  (In TCP, sequence number modification is required
    to support protocols like FTP that carry variable-length addresses in
    the data stream.  If such an application were deployed over DCCP,
    middleboxes would simply grow or shrink the relevant packets as
    necessary without changing their sequence numbers.  This might
    involve fragmenting the packet.)

It would be nice for BEHAVE to not needlessly contradict this.


(2) REQ-13: This one is less important.  The RFC4340 text says:

    The Service Code field in DCCP-Request packets provides information
    that may be useful for stateful middleboxes.  With Service Code, a
    middlebox can tell what protocol a connection will use without
    relying on port numbers.  Middleboxes can disallow connections that
    attempt to access unexpected services by sending a DCCP-Reset with
    Reset Code 8, "Bad Service Code".  Middleboxes should not modify the
    Service Code unless they are really changing the service a connection
    is accessing.

One can imagine useful ALG middleboxes that would change a connection's 
service, and therefore its Service Code, and I don't see what's gained by a 
"MUST NOT" requirement.  This is speculative however.

Eddie



Dan Wing wrote:
> Behave is commencing a 2-week WGLC for "Network Address Translation (NAT)
> Behavioral Requirements for DCCP",
> <http://tools.ietf.org/html/draft-ietf-behave-dccp-01>.  The WGLC will end on
> August 21.
> 
> Please send comments to the author and to Behave.
> 
> -d
> 
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug  8 08:32:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DB1F3A6914;
	Fri,  8 Aug 2008 08:32:48 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 461713A6C8E;
	Fri,  8 Aug 2008 07:28:20 -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 ULmkvsVRbEvS; Fri,  8 Aug 2008 07:28:19 -0700 (PDT)
Received: from sonussf2.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27])
	by core3.amsl.com (Postfix) with ESMTP id A1D503A6AD9;
	Fri,  8 Aug 2008 07:28:17 -0700 (PDT)
Received: from sonusmail06.sonusnet.com (sonusmail06.sonusnet.com
	[10.128.32.156])
	by sonussf2.sonusnet.com (8.13.7/8.13.7) with ESMTP id m78ES7GZ027888; 
	Fri, 8 Aug 2008 10:28:07 -0400
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 8 Aug 2008 10:28:06 -0400
Message-ID: <97D8957C5565BB41912C3F958914C49F05F4E7E8@sonusmail06.sonusnet.com>
In-Reply-To: <214901c8f8f5$7d5ea610$d35d150a@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dccp] WGLC: draft-ietf-behave-dccp-01
Thread-index: Acj49Xzun/wVC6D6QQCAcBe4RCQB+AAaWLjg
From: "Phelan, Tom" <tphelan@sonusnet.com>
To: "Dan Wing" <dwing@cisco.com>, "Behave WG" <behave@ietf.org>
X-Mailman-Approved-At: Fri, 08 Aug 2008 08:32:46 -0700
Cc: dccp@ietf.org, rem@videolan.org
Subject: Re: [BEHAVE] [dccp] WGLC: draft-ietf-behave-dccp-01
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi Remi,

Here are some comments.

Tom P.

Section 4.3:

"o  The filtering behavior for DCCP MAY be independent of the filtering
behavior for UDP."

Shouldn't that be "for UDP or any other protocol" or something similar.
Certainly it's acceptable for the DCCP filtering behavior to be
independent of TCP...

"REQ-4: A NAT MUST NOT respond to an unsolicited inbound DCCP-Listen
packet for at least 6 seconds after the packet is received."

What does "not respond" mean?  Not send the ICMP message? Not forward
the DCCP-Listen packet?  Both?  Maybe this could be clearer if it's
reworded in a positive vein -- "Upon receiving a DCCP-Listen packet a
NAT MUST..."

Section 5, REQ-5:

Is this saying that the "established connection idle timeout" cannot be
configured to be less than 2 hours 40 minutes?  I see this language is
stolen directly from behave-tcp, but I find it confusing.

Section 6:

The first paragraph seems inaccurate to me.  It's actually much easier
to modify the payload in DCCP than it is in TCP.  As long as the
modified packet remains within the PMTU, you don't have to do anything
to the DCCP header except adjust the checksum -- you certainly don't
need to modify the sequence numbers.  You would only need to modify the
sequence numbers if you added a packet.  Of course changing the packet
size *might* foul up the application, but the purpose of an ALG is to be
application-aware, and so it would be highly unlikely to do something
that would foul up the application.

I agree with the intent here -- no ALGS -- but I don't think your
argument justifies it.  Maybe something more along the line of no DCCP
applications currently need ALGs, so let's keep it that way.

Section 10:

Somehow I think an empty security considerations section isn't going to
fly :-).  I suppose you could start by referencing the behave-tcp
security issues and describe what's different here.

General:

Your use of RFC 4787 terms isn't identical to RFC 4787.  For example,
you use "endpoint independent mapping" and RFC 4787 uses
"endpoint-independent mapping" -- it makes it difficult to look up the
meaning of the terms.


> -----Original Message-----
> From: dccp-bounces@ietf.org [mailto:dccp-bounces@ietf.org] On Behalf
Of
> Dan Wing
> Sent: Thursday, August 07, 2008 9:24 PM
> To: Behave WG
> Cc: dccp@ietf.org; rem@videolan.org
> Subject: [dccp] WGLC: draft-ietf-behave-dccp-01
> 
> Behave is commencing a 2-week WGLC for "Network Address Translation
(NAT)
> Behavioral Requirements for DCCP",
> <http://tools.ietf.org/html/draft-ietf-behave-dccp-01>.  The WGLC will
end
> on
> August 21.
> 
> Please send comments to the author and to Behave.
> 
> -d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug  8 13:08:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E09C43A69F5;
	Fri,  8 Aug 2008 13:08:52 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D8D73A69F5
	for <behave@core3.amsl.com>; Fri,  8 Aug 2008 13:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 QHJh4hc5iCnB for <behave@core3.amsl.com>;
	Fri,  8 Aug 2008 13:08:51 -0700 (PDT)
Received: from mail-07.primus.ca (mail8.primus.ca [216.254.141.175])
	by core3.amsl.com (Postfix) with ESMTP id DB00C3A69B9
	for <behave@ietf.org>; Fri,  8 Aug 2008 13:08:50 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-07.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KRYGO-0002mH-0I; Fri, 08 Aug 2008 16:08:40 -0400
Message-Id: <7EC2DFA4-F444-425E-8478-FDA531322F45@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Benny Prijono <bennylp@pjsip.org>
In-Reply-To: <1879720d0807311438k3a90e41dm939dfb16fa047b31@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 8 Aug 2008 16:08:40 -0400
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
	<1879720d0807311438k3a90e41dm939dfb16fa047b31@mail.gmail.com>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0424858657=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--===============0424858657==
Content-Type: multipart/alternative; boundary=Apple-Mail-44--599247629


--Apple-Mail-44--599247629
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Thu, 31-Jul-08, at 17:38 , Benny Prijono wrote:

> On Thu, Jul 31, 2008 at 3:03 AM, Philip Matthews <philip_matthews@magma.ca 
> > wrote:
> There was an ad-hoc meeting on TURN  on Wednesday, July 31. During  
> this meeting, all the open issues affecting TURN were discussed and  
> proposals for how to resolve them reached. Jonathan and I then held  
> a phone call to discuss and in a couple of cases made minor tweaks.  
> This e-mail documents the proposed resolutions. Please comment if  
> you are not happy with any of these.
>
>   1.  Detecting in-use channels.  Do we need a way for a client to
>       determine if a channel is currently bound?  Right now, the only
>       way is to try to bind it to an address.
>
> This issue was prompted by concerns that the client and server might  
> get out-of-sync over which channels were bound. A concrete example  
> of this concern was when a client retransmitted a ChannelBind msg  
> over UDP. If the first transmission generated a failure response,  
> but the second generated a success response, then the client would  
> believe that the channel was not bound, but the server would believe  
> the channel is bound.
>
>
> I thought that (as per the last discussion on this list), any STUN  
> servers (TURN included) MUST retransmit the last error response upon  
> receiving request retransmissions, so this shouldn't be an issue,  
> should it?

The current version of the STUN spec (draft-ietf-behave-rfc3489bis-18)  
lists this as a SHOULD.

However, I believe you are right -- if the server remembers and  
retransmits error responses, then there is no problem.

>
>
>
> The proposed resolution to this issue is to not add any way for the  
> client to determine which channels are bound, but to add text  
> explicitly saying that a client should abandon an allocation if it  
> receives an error response to a ChannelBind command. The idea is  
> that any mismatch between the client and the server in this area is  
> very serious, and starting over is the best way to recover.
>
>
> I don't think I would like the text. First of all, not all error  
> responses means out of sync (for example, 438/Stale Nonce). Second,  
> I feel that it should be left to client to decide what to do when  
> such mismatch happens (which shouldn't happen in the first place  
> because of error retransmission requirement above).
>
> So the solution does not solve the question. And personally I don't  
> think this is a question that needs to be solved either, since  
> client totally controls the channel numbers, and out-of-sync can't  
> happen if server retransmits error responses.

How about the following text? This is an attempt to give guidance  
while leaving the final decision of what to do up to the implementor.

10.3.  Receiving a ChannelBind Response

    When the client receives a ChannelBind success response, it updates
    its data structures to record that the channel binding is now  
active.

    If the client receives a ChannelBind failure response that indicates
    that the channel information is out-of-sync between the client and
    the server (e.g., an unexpected 400 "Bad Request" response), then it
    is RECOMMENDED that the client immediately delete the allocation and
    start afresh with a new allocation.

- Philip
--Apple-Mail-44--599247629
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><html>On Thu, =
31-Jul-08, at 17:38 , Benny Prijono wrote:</html><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
dir=3D"ltr">On Thu, Jul 31, 2008 at 3:03 AM, Philip Matthews <span =
dir=3D"ltr">&lt;<a =
href=3D"mailto:philip_matthews@magma.ca">philip_matthews@magma.ca</a>></sp=
an> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt =
0.8ex; padding-left: 1ex;"> There was an ad-hoc meeting on TURN &nbsp;on =
Wednesday, July 31. During this meeting, all the open issues affecting =
TURN were discussed and proposals for how to resolve them reached. =
Jonathan and I then held a phone call to discuss and in a couple of =
cases made minor tweaks. This e-mail documents the proposed resolutions. =
Please comment if you are not happy with any of these.<br> <br> &nbsp; =
1. &nbsp;Detecting in-use channels. &nbsp;Do we need a way for a client =
to<br> &nbsp; &nbsp; &nbsp; determine if a channel is currently bound? =
&nbsp;Right now, the only<br> &nbsp; &nbsp; &nbsp; way is to try to bind =
it to an address.<br> <br> This issue was prompted by concerns that the =
client and server might get out-of-sync over which channels were bound. =
A concrete example of this concern was when a client retransmitted a =
ChannelBind msg over UDP. If the first transmission generated a failure =
response, but the second generated a success response, then the client =
would believe that the channel was not bound, but the server would =
believe the channel is bound.<br> <br> </blockquote><div><br>I thought =
that (as per the last discussion on this list), any STUN servers (TURN =
included) MUST retransmit the last error response upon receiving request =
retransmissions, so this shouldn't be an issue, should =
it?</div></div></div></blockquote><div><br></div>The current version of =
the STUN spec (draft-ietf-behave-rfc3489bis-18) lists this as a =
SHOULD.</div><div><br></div><div>However, I believe you are right -- if =
the server remembers and retransmits error responses, then there is no =
problem.</div><div><br><blockquote type=3D"cite"><div dir=3D"ltr"><div =
class=3D"gmail_quote"><div><br> <br>&nbsp;</div><blockquote =
class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, =
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The proposed =
resolution to this issue is to not add any way for the client to =
determine which channels are bound, but to add text explicitly saying =
that a client should abandon an allocation if it receives an error =
response to a ChannelBind command. The idea is that any mismatch between =
the client and the server in this area is very serious, and starting =
over is the best way to recover.<br> <br> </blockquote></div><br>I don't =
think I would like the text. First of all, not all error responses means =
out of sync (for example, 438/Stale Nonce). Second, I feel that it =
should be left to client to decide what to do when such mismatch happens =
(which shouldn't happen in the first place because of error =
retransmission requirement above). <br> <br>So the solution does not =
solve the question. And personally I don't think this is a question that =
needs to be solved either, since client totally controls the channel =
numbers, and out-of-sync can't happen if server retransmits error =
responses.</div></blockquote><div><br></div><div>How about the following =
text? This is an attempt to give guidance while leaving the final =
decision of what to do up to the =
implementor.</div><div><br></div><div><div>10.3. &nbsp;Receiving a =
ChannelBind Response</div><div><br></div><div>&nbsp;&nbsp; When the =
client receives a ChannelBind success response, it =
updates</div><div>&nbsp;&nbsp; its data structures to record that the =
channel binding is now active.</div><div><br></div><div>&nbsp;&nbsp; If =
the client receives a ChannelBind failure response that =
indicates</div><div>&nbsp;&nbsp; that the channel information is =
out-of-sync between the client and</div><div>&nbsp;&nbsp; the server =
(e.g., an unexpected 400 "Bad Request" response), then =
it</div><div>&nbsp;&nbsp; is RECOMMENDED that the client immediately =
delete the allocation and</div><div>&nbsp;&nbsp; start afresh with a new =
allocation.</div><div><br></div></div><div>- =
Philip</div></div></body></html>=

--Apple-Mail-44--599247629--

--===============0424858657==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

--===============0424858657==--


From behave-bounces@ietf.org  Fri Aug  8 13:35:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A21A3A6A94;
	Fri,  8 Aug 2008 13:35:24 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 812D63A6A94
	for <behave@core3.amsl.com>; Fri,  8 Aug 2008 13:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.605
X-Spam-Level: 
X-Spam-Status: No, score=-0.605 tagged_above=-999 required=5
	tests=[AWL=-1.994, BAYES_00=-2.599, FRT_STOCK2=3.988]
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 kSZbnSZlJ4em for <behave@core3.amsl.com>;
	Fri,  8 Aug 2008 13:35:22 -0700 (PDT)
Received: from mail-08.primus.ca (mail8.primus.ca [216.254.141.175])
	by core3.amsl.com (Postfix) with ESMTP id 013853A63C9
	for <behave@ietf.org>; Fri,  8 Aug 2008 13:35:21 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-08.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KRYgE-0006rh-08; Fri, 08 Aug 2008 16:35:22 -0400
Message-Id: <4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Alfred E. Heggestad <aeh@db.org>
In-Reply-To: <48949422.4080103@db.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 8 Aug 2008 16:35:19 -0400
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
	<48949422.4080103@db.org>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks for your comments. Responses inline.
- Philip

On Sat, 2-Aug-08, at 13:06 , Alfred E. Heggestad wrote:
> Hi
>
> please see inline for my comments:
>
>
> Philip Matthews wrote:
>> There was an ad-hoc meeting on TURN  on Wednesday, July 31. During  
>> this meeting, all the open issues affecting TURN were discussed and  
>> proposals for how to resolve them reached. Jonathan and I then held  
>> a phone call to discuss and in a couple of cases made minor tweaks.  
>> This e-mail documents the proposed resolutions. Please comment if  
>> you are not happy with any of these.
>>   1.  Detecting in-use channels.  Do we need a way for a client to
>>       determine if a channel is currently bound?  Right now, the only
>>       way is to try to bind it to an address.
>> This issue was prompted by concerns that the client and server  
>> might get out-of-sync over which channels were bound. A concrete  
>> example of this concern was when a client retransmitted a  
>> ChannelBind msg over UDP. If the first transmission generated a  
>> failure response, but the second generated a success response, then  
>> the client would believe that the channel was not bound, but the  
>> server would believe the channel is bound.
>> The proposed resolution to this issue is to not add any way for the  
>> client to determine which channels are bound, but to add text  
>> explicitly saying that a client should abandon an allocation if it  
>> receives an error response to a ChannelBind command. The idea is  
>> that any mismatch between the client and the server in this area is  
>> very serious, and starting over is the best way to recover.
>
> I dont see any need for detecting in-use channels.
>
> the TURN client is controlling which channels are in use, and the
> chances of a ChannelBind error response is very low.

OK. See my suggested text in the message to Benny Prijono sent a few  
minutes ago.

>
>
>
>> -- 
>>   2.  Public TURN servers.  The spec currently hints (but does not  
>> say
>>       anything solid) that the way to run a publicly-accessable TURN
>>       server is to not require authentication.  But perhaps a better
>>       way is to require authentication but have some unspecified  
>> method
>>       to allow any user to create an account on the server.
>> After discussion in the ad-hoc, we propose to say nothing about  
>> this. The current text, which does really say anything about this,  
>> would remain unchanged. The rationale is that this is a protocol  
>> document, not an operational guidance document.
>
> Fully agree
>
>
>> -- 
>>   3.  IPv6.  Currently, TURN supports IPv4-to-IPv4 relaying, and  
>> IPv6-
>>       to-IPv6 relaying, but does not support IPv4-to-IPv6  
>> relaying.  To
>>       ensure this, a server requires that the family of the relayed
>>       address match that of the 5-tuple as seen by the server.
>>       However, some people would like to see a different rule.
>> The proposed resolution is to move the specification of IPv6-to- 
>> IPv6, IPv4-to-IPv6, and IPv6-to-IPv4 relaying to draft-ietf-behave- 
>> turn-ipv6. The base TURN specification would handle only IPv4-to- 
>> IPv4 relaying. The base spec would say that the server address and  
>> all relayed addresses must be IPv4 addresses.
>> This proposal ensures that client can know in advance what family  
>> (v4 or v6) the relayed-transport-address returned by the server  
>> will always be of. Some people had objected to the scheme in  
>> TURN-09 because the client might send the Allocate request over  
>> IPv6, but unbeknownst to the client, the request might pass through  
>> a NAT64 and arrive at the server at an IPv4 address. If this  
>> happened, the client would get back an IPv4 relayed-transport- 
>> address when it really wanted an IPv6 relayed-transport-address.  
>> This proposal addresses their concern, while also moving all the  
>> complexity around IPv6 and IPv4 <-> IPv6 to draft-ietf-behave-turn- 
>> ipv6, where we have more time to study it and get it right.
>
> Agreed.
>
>
>> -- 
>>   4.  ALTERNATE-SERVER and Anycast.  The details of ALTERNATE-SERVER
>>       support are still under discussion.  In particular, some people
>>       would like to use ALTERNATE-SERVER to support anycast discovery
>>       of a TURN server.
>> The proposed resolution is as follows:
>> a) The TURN spec would allow the use of ALTERNATE-SERVER in replies  
>> to Allocate requests. Furthermore, the text would override the STUN  
>> spec and allow the use of ALTERNATE-SERVER in unauthenticated  
>> Allocate error responses. If the client receives such a response,  
>> then the client SHOULD retry the Allocate transaction with the new  
>> address. However, the client MUST check that the realm value  
>> received back from the new server is as expected and must use the  
>> same username and password as it would have with the original  
>> server. In practice, this means that the client must have known in  
>> advance what realm, username and password to use with the original  
>> server, and uses these same values with the alternate server. With  
>> this check, the client can ensure that the original and alternate  
>> server are part of the same authentication group.
>> b) The spec would NOT go into detail on how this mechanism can be  
>> used to do anycast discovery. This would be left to another document.
>> In summary, the spec would provide the basic pieces required, but  
>> would not go into details on how to use those pieces.
>
> I dont have any opinion about this..
>
>
>> -- 
>>   5.  Authenticated Permission Refresh.  Currently, permissions can  
>> be
>>       refreshed by unauthenticated Send indications and ChannelData
>>       messages.  Some have suggested that this is a security issue.
>> The discussion of this issue at the BEHAVE meeting on Tuesday was  
>> inconclusive. At the ad-hoc, there was further discussion and it  
>> was realized that the attack described in the slides presented at  
>> the BEHAVE meeting was easier to perform that we realized earlier.  
>> Given this realization, the people at the ad-hoc meeting agreed on  
>> the following (options 3 and 4 combined from the slides):
>> a) In addition to a Send indication, TURN will support a Send  
>> request/response transaction.
>> b) Permissions will no longer be installed or refreshed by Send  
>> indications or ChannelData msgs. Instead, permissions will be  
>> installed or refreshed by ChannelBind transactions (as in turn-09)  
>> and by the new Send request/response transaction. Since both of  
>> these are request/response, they can be authenticated.
>> c) The semantics of the new Send request/response is very similar  
>> to the existing Send indication: it would take the same attributes,  
>> etc. Specifically, it would have two forms: one with and one  
>> without the DATA attribute; the 'without' form would only install  
>> or refresh permissions, while the 'with' form would also send data.
>> d) In addition, the client would check that Data messages are being  
>> received from peer with which it thinks it has a permission. If the  
>> client believes there is no permission, the client would discard  
>> the data.
>
> I will strongly suggest that any protocol changes to solve this, is
> carefully reviewed by experts in this working group. I have been  
> running
> the current permission/channel mechanism (defined in turn-07/08/09)
> for a while now, and it shows that it is very elegant and clean and  
> robust.
> I have not seen any problems with it in deployment.
>
> I am very worried that if we change the turn-spec to add Send  
> Request/Response,
> we will indirectly add new problems that we did not think of.

This was a hotly debated point at the BEHAVE meeting and it took quite  
a while to come to a consensus. But yes, any change is worrisome.

>
>
> for each TURN allocation, both the client and the server must  
> maintain a list
> of channels in use. The same thing would then also apply for  
> Permissions, as
> both client and server must maintain a list of permissions (per  
> alloation).
> if we can live with the increased security of checking permissions  
> in the
> TURN client (SHOULD-strength?), then I would be voting for this  
> solution.

Could you explain your last sentence in more detail? I am not sure  
what you are referring to.

>
>
>
>
>> -- 
>>   6.  PMTUD for non-preserving allocations.  Some people would like a
>>       way to do PMTUD even if the allocation is non-preserving, and
>>       have suggested that a way for the client to indicate to the
>>       server (in a Send indication) that the DF bit should be set  
>> when
>>       sending to the peer might allow this.
>> There was hot discussion of this issue at the ad-hoc. Finally, it  
>> was agreed that the mechanism suggested by Cullen would be added to  
>> the TURN specification, to whit:
>> a) A new attribute would be defined for use in a Send indication.  
>> If this attribute is present, then the server would set the DF bit  
>> when sending the UDP datagram to the peer.
>
> if this is really required, I would suggest moving the attribute/bit
> to the allocate request instead. setting the DF-bit is normally done
> when opening a socket (setsockopt IP_MTU_DISCOVER)

Cullen Jennings, who was the person who pushed strongly for this  
feature, would like to set the DF bit on some packets but not others.

>
>
> as a side note, it would be nice to have more fine-grained control
> with how the allocation/server should behave. I mean instead of having
> a bit-flag saying non-preserving/preserving, we could add more bits
> which describe each feature for that allocation.
>
> the client would request a feature by setting a bit to 1, the server
> would include in the response which features it supports (0==disabled,
> 1==enabled).

If I understand you correctly, then you would like to be able to  
request the features associated with a preserving allocation  
individually rather than get them all together. However, all the  
specification on preserving allocations has been moved out of the base  
TURN spec to a new (as yet unpublished) document. Let's have this  
discussion once that document is ready.

>
>
>
>
>> -- 
>>   7.  Security.  The security consideration section is out-of-date  
>> with
>>       the changes to the rest of the draft, and it has been suggested
>>       that TURN might require TLS to provide proper security.   
>> Updating
>>       the security consideration section will answer this question.
>> The above changes fix all known security holes. Never-the-less, the  
>> authors plan to rewrite the security considerations section ASAP,  
>> which would involve taking another hard look at TURN security.
>
> [...]
>
>
> /alfred
>
>> Comments?
>> - Philip
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug  8 13:40:42 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 391F33A67EE;
	Fri,  8 Aug 2008 13:40:42 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 39D4C3A63C9
	for <behave@core3.amsl.com>; Fri,  8 Aug 2008 13:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74]
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 xwAZM8WoszQG for <behave@core3.amsl.com>;
	Fri,  8 Aug 2008 13:40:39 -0700 (PDT)
Received: from mail.sipeerior.com (mail.sipeerior.com [70.169.152.168])
	by core3.amsl.com (Postfix) with ESMTP id 724543A6969
	for <behave@ietf.org>; Fri,  8 Aug 2008 13:40:39 -0700 (PDT)
Received: from vuelta.local (ip68-230-194-34.rd.hr.cox.net [68.230.194.34])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.sipeerior.com (Postfix) with ESMTPSA id 31FF343A131;
	Fri,  8 Aug 2008 16:10:23 -0400 (EDT)
Message-ID: <489CAF40.6010304@sipeerior.com>
Date: Fri, 08 Aug 2008 16:40:32 -0400
From: Bruce Lowekamp <lowekamp@sipeerior.com>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>
Cc: Jeremy Beker <gothmog@confusticate.com>
Subject: [BEHAVE] FlexNES: Flexible NAT Emulation Software
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


FlexNES is a tool for a linux router that allows the emulation of 
different NAT behaviors.  It works by using iptables to filter packets 
and pass them through a user-level application that performs the NAT 
behavior before passing them back through iptables.   It currently is 
limited to UDP (its goal was to reproduce all of the different good and 
bad behaviors in 4787), but the general architecture should be 
extensible to other protocols.

FlexNES is available under the GPLv2 license.  Jeremey Beker wrote the 
software as his MS project for the College of William and Mary CS 
Department.  I was his advisor for the project.

FlexNES is available at

http://code.google.com/p/flexnes/

We hope that this tool is useful for everyone who wants to test their 
software's behavior behind different types of NATs (without the need to 
have stacks of NATs in a rack).  If you find it useful, please help by 
contributing back to the project with improvements.

Bruce

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug  8 17:08:57 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B67B93A69FE;
	Fri,  8 Aug 2008 17:08:57 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3DA1B3A69FE
	for <behave@core3.amsl.com>; Fri,  8 Aug 2008 17:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.277
X-Spam-Level: 
X-Spam-Status: No, score=-98.277 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FRT_STOCK2=3.988, IP_NOT_FRIENDLY=0.334,
	USER_IN_WHITELIST=-100]
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 ayBFUZPlIjEz for <behave@core3.amsl.com>;
	Fri,  8 Aug 2008 17:08:55 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 892523A6924
	for <behave@ietf.org>; Fri,  8 Aug 2008 17:08:55 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id 71D947F032C; Sat,  9 Aug 2008 00:08:52 +0000 (UTC)
Received: from [192.168.1.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id B6BBC7F0314;
	Sat,  9 Aug 2008 00:08:48 +0000 (UTC)
Message-ID: <489CE00F.3050500@acm.org>
Date: Fri, 08 Aug 2008 17:08:47 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>	<48949422.4080103@db.org>
	<4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
In-Reply-To: <4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
> Thanks for your comments. Responses inline.
> - Philip
> 

[...]

> 
>>
>>
>>
>>
>>> -- 
>>>   6.  PMTUD for non-preserving allocations.  Some people would like a
>>>       way to do PMTUD even if the allocation is non-preserving, and
>>>       have suggested that a way for the client to indicate to the
>>>       server (in a Send indication) that the DF bit should be set when
>>>       sending to the peer might allow this.
>>> There was hot discussion of this issue at the ad-hoc. Finally, it was
>>> agreed that the mechanism suggested by Cullen would be added to the
>>> TURN specification, to whit:
>>> a) A new attribute would be defined for use in a Send indication. If
>>> this attribute is present, then the server would set the DF bit when
>>> sending the UDP datagram to the peer.
>>
>> if this is really required, I would suggest moving the attribute/bit
>> to the allocate request instead. setting the DF-bit is normally done
>> when opening a socket (setsockopt IP_MTU_DISCOVER)
> 
> Cullen Jennings, who was the person who pushed strongly for this
> feature, would like to set the DF bit on some packets but not others.
> 

I also support this feature.

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug  8 17:14:44 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41E4D3A6905;
	Fri,  8 Aug 2008 17:14:44 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C02E3A6905
	for <behave@core3.amsl.com>; Fri,  8 Aug 2008 17:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 uv4wBpC8Umun for <behave@core3.amsl.com>;
	Fri,  8 Aug 2008 17:14:42 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id C76773A687A
	for <behave@ietf.org>; Fri,  8 Aug 2008 17:14:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,330,1215388800"; d="scan'208";a="137718871"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 09 Aug 2008 00:14:40 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m790Eefb021206; 
	Fri, 8 Aug 2008 17:14:40 -0700
Received: from dwingwxp01 (dhcp-128-107-163-234.cisco.com [128.107.163.234])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m790EeDn028765;
	Sat, 9 Aug 2008 00:14:40 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
Date: Fri, 8 Aug 2008 17:14:40 -0700
Message-ID: <004a01c8f9b4$ea9211d0$361e6b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj5tOpuDcBQFYS5SpS3iHKxXrA6RA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=496; t=1218240880; x=1219104880;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20TURN=20URI,=20draft-petithuguenin-behave-turn-u ri
	|Sender:=20; bh=aYWR/bU3a11fKmkXwBuILt6gmpY8lA8VG+V32LupJww=;
	b=g5cVTCRTIC0felj7pOKGzWP4FSYltC+eXSNXbmar5QLlMFvppLnaTjM9xb
	GGewhfI4t7f1qBglk/YwFK2lnLBC6rIv7WUQj1nNeQZOjvF8il4dYDmO7EAZ
	JLEwxvDIk4;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [BEHAVE] TURN URI, draft-petithuguenin-behave-turn-uri
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

At the IETF meeting in Dublin, Marc gave a presentation on "Traversal Using
Relays around NAT (TURN) Uniform Resource Identifiers",
http://tools.ietf.org/html/draft-petithuguenin-behave-turn-uri-02.

At the meeting, there wasn't much interest (positive or negative) for this
draft.  

Please speak up -- for or against -- this draft.  If there is interest in this
draft, I will propose we add a milestone for it; otherwise it will probably go
forward as an individual submission.

-d


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug  8 18:11:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 057B03A6C86;
	Fri,  8 Aug 2008 18:11:05 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 390233A6C86
	for <behave@core3.amsl.com>; Fri,  8 Aug 2008 18:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.392
X-Spam-Level: 
X-Spam-Status: No, score=0.392 tagged_above=-999 required=5 tests=[AWL=-0.997, 
	BAYES_00=-2.599, FRT_STOCK2=3.988]
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 KqI+omimh8Gv for <behave@core3.amsl.com>;
	Fri,  8 Aug 2008 18:11:03 -0700 (PDT)
Received: from mail-09.primus.ca (mail9.primus.ca [216.254.141.176])
	by core3.amsl.com (Postfix) with ESMTP id 65C3C3A6A5C
	for <behave@ietf.org>; Fri,  8 Aug 2008 18:11:03 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-09.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KRcz1-00049l-1m; Fri, 08 Aug 2008 21:11:03 -0400
Message-Id: <4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Marc Petit-Huguenin <petithug@acm.org>, "Alfred E. Heggestad" <aeh@db.org>
In-Reply-To: <489CE00F.3050500@acm.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 8 Aug 2008 21:10:58 -0400
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>	<48949422.4080103@db.org>
	<4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
	<489CE00F.3050500@acm.org>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Fri, 8-Aug-08, at 20:08 , Marc Petit-Huguenin wrote:
>>> if this is really required, I would suggest moving the attribute/bit
>>> to the allocate request instead. setting the DF-bit is normally done
>>> when opening a socket (setsockopt IP_MTU_DISCOVER)
>>
>> Cullen Jennings, who was the person who pushed strongly for this
>> feature, would like to set the DF bit on some packets but not others.
>>
>
> I also support this feature.

After thinking about this feature a bit, and taking Alfred's comment  
into account, it seems to me that there might be a platform where this  
feature cannot be implemented with an unprivileged user-space  
implementation. For example, a quick web search on how to do this for  
MacOS seemed to indicate that there might be a problem. Without  
getting into a discussion of which platforms can and cannot do it, it  
seems wise to me to treat this as a feature which an implementation  
might not be willing or able to support.

Hence I have the following proposal for how to define this feature:

1) TURN would define a new attribute, call it SET-DF. The attribute  
would have a value length of 0. The attribute would be in the  
comprehension-required range.

2) A client MAY include the SET-DF option in an Allocate request.  
Including this option means that the client is requesting an  
allocation that supports this feature.

3) If the server cannot create an allocation that supports the  
feature, the Allocate request is rejected with a 420 Unknown  
Attributes and the UNKNOWN-ATTRIBUTES attribute would list this  
attribute. [Note that in this case, the SET-DF attribute may not  
really be unknown, but simply cannot be supported.]

4) If the server accepts the Allocate request, then the client MAY use  
the SET-DF attribute in a Send request or a Send indication. If the  
attribute is included, then the server sets the DF bit in the  
corresponding UDP datagram towards the peer. If the attribute is not  
included, the server does not set the DF bit.

5) Using the SET-DF attribute in a Send request or Send indication on  
an allocation that does not support it causes the Send request to be  
rejected and the Send indication to be silently ignored (= standard  
behavior for a unknown comprehension-required attribute).

An alternative to this would be to drop points (2) and (3), and say  
that the server rejects a Send request if it cannot	 support the SET- 
DF attribute. This is a bit simpler, but delays the point at which the  
client discovers that the attribute is not supported.

Comments?

- Philip
  
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat Aug  9 05:44:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E01963A6BAB;
	Sat,  9 Aug 2008 05:44:04 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D6243A6BAB
	for <behave@core3.amsl.com>; Sat,  9 Aug 2008 05:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.277
X-Spam-Level: 
X-Spam-Status: No, score=-98.277 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FRT_STOCK2=3.988, IP_NOT_FRIENDLY=0.334,
	USER_IN_WHITELIST=-100]
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 zMp9JSXtY752 for <behave@core3.amsl.com>;
	Sat,  9 Aug 2008 05:44:02 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 66F303A6A5D
	for <behave@ietf.org>; Sat,  9 Aug 2008 05:44:02 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id E0E987F032E; Sat,  9 Aug 2008 12:44:02 +0000 (UTC)
Received: from [192.168.1.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id A83237F0314;
	Sat,  9 Aug 2008 12:43:57 +0000 (UTC)
Message-ID: <489D910D.7020009@acm.org>
Date: Sat, 09 Aug 2008 05:43:57 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>	<48949422.4080103@db.org>
	<4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
	<489CE00F.3050500@acm.org>
	<4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
In-Reply-To: <4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
> 
> On Fri, 8-Aug-08, at 20:08 , Marc Petit-Huguenin wrote:
>>>> if this is really required, I would suggest moving the attribute/bit
>>>> to the allocate request instead. setting the DF-bit is normally done
>>>> when opening a socket (setsockopt IP_MTU_DISCOVER)
>>>
>>> Cullen Jennings, who was the person who pushed strongly for this
>>> feature, would like to set the DF bit on some packets but not others.
>>>
>>
>> I also support this feature.
> 
> After thinking about this feature a bit, and taking Alfred's comment
> into account, it seems to me that there might be a platform where this
> feature cannot be implemented with an unprivileged user-space
> implementation. For example, a quick web search on how to do this for
> MacOS seemed to indicate that there might be a problem. Without getting
> into a discussion of which platforms can and cannot do it, it seems wise
> to me to treat this as a feature which an implementation might not be
> willing or able to support.
> 
> Hence I have the following proposal for how to define this feature:
> 
> 1) TURN would define a new attribute, call it SET-DF. The attribute
> would have a value length of 0. The attribute would be in the
> comprehension-required range.
> 
> 2) A client MAY include the SET-DF option in an Allocate request.
> Including this option means that the client is requesting an allocation
> that supports this feature.
> 
> 3) If the server cannot create an allocation that supports the feature,
> the Allocate request is rejected with a 420 Unknown Attributes and the
> UNKNOWN-ATTRIBUTES attribute would list this attribute. [Note that in
> this case, the SET-DF attribute may not really be unknown, but simply
> cannot be supported.]
> 
> 4) If the server accepts the Allocate request, then the client MAY use
> the SET-DF attribute in a Send request or a Send indication. If the
> attribute is included, then the server sets the DF bit in the
> corresponding UDP datagram towards the peer. If the attribute is not
> included, the server does not set the DF bit.
> 
> 5) Using the SET-DF attribute in a Send request or Send indication on an
> allocation that does not support it causes the Send request to be
> rejected and the Send indication to be silently ignored (= standard
> behavior for a unknown comprehension-required attribute).
> 
> An alternative to this would be to drop points (2) and (3), and say that
> the server rejects a Send request if it cannot     support the SET-DF
> attribute. This is a bit simpler, but delays the point at which the
> client discovers that the attribute is not supported.
> 
> Comments?

Here's an alternate proposal:

- Use bit 3 in REQUESTED-PROPS for the support of the DF bit.  This is
consistent with the usage of REQUESTED-PROPS to query/request allocation
properties.

- Redefine the reserved first 8 bits of PEER-ADDRESS to use bit 7 to
carry the DF bit.  It can then be used in a Send indication/transaction
and even in a ChannelBind transaction if one wants DF bit set in all
packets.

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat Aug  9 05:59:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D8593A6BFE;
	Sat,  9 Aug 2008 05:59:49 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C0363A6BFE
	for <behave@core3.amsl.com>; Sat,  9 Aug 2008 05:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
	tests=[BAYES_50=0.001]
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 N1jtSC8A0b6K for <behave@core3.amsl.com>;
	Sat,  9 Aug 2008 05:59:47 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 3AAA83A68B9
	for <behave@ietf.org>; Sat,  9 Aug 2008 05:59:47 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id 377BB29E14DD; Sat,  9 Aug 2008 08:59:18 -0400 (EDT)
Received: from [192.168.1.100] (ip216-239-82-59.vif.net [216.239.82.59])
	by jazz.viagenie.ca (Postfix) with ESMTP id 2079729E1433
	for <behave@ietf.org>; Sat,  9 Aug 2008 08:59:18 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
Organization: =?utf-8?q?Viag=C3=A9nie?=
To: behave@ietf.org
Date: Sat, 9 Aug 2008 08:59:17 -0400
User-Agent: KMail/1.9.9
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
	<489CE00F.3050500@acm.org>
	<4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
In-Reply-To: <4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808090859.17372.simon.perreault@viagenie.ca>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Friday 08 August 2008 21:10:58 Philip Matthews wrote:
> An alternative to this would be to drop points (2) and (3), and say
> that the server rejects a Send request if it cannot	 support the SET-
> DF attribute. This is a bit simpler, but delays the point at which the
> client discovers that the attribute is not supported.

I prefer this alternative. KISS. Logically, setting the DF bit is not an 
allocation attribute so it looks like a hack to save one round trip. Not a 
good enough reason IMHO.

BTW, instead of SET-DF perhaps DONT-FRAGMENT would be more appropriate.

-- 
Please try Numb, a STUN/TURN server implementation.
Free access at http://numb.viagenie.ca/.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun Aug 10 18:08:15 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5910528C1F3;
	Sun, 10 Aug 2008 18:08:15 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AB1128C1F3
	for <behave@core3.amsl.com>; Sun, 10 Aug 2008 18:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.752
X-Spam-Level: 
X-Spam-Status: No, score=-100.752 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74, FRT_STOCK2=3.988, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
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 KPrMLK0Dfqow for <behave@core3.amsl.com>;
	Sun, 10 Aug 2008 18:08:13 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 84F2928C10F
	for <behave@ietf.org>; Sun, 10 Aug 2008 18:08:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,341,1215388800"; d="scan'208";a="138296320"
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-6.cisco.com with ESMTP; 11 Aug 2008 01:08:15 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id m7B18Fh2002717; 
	Sun, 10 Aug 2008 18:08:15 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with SMTP id m7B18ECS005461;
	Mon, 11 Aug 2008 01:08:14 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: Philip Matthews <philip_matthews@magma.ca>
In-Reply-To: <4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>	<48949422.4080103@db.org>
	<4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
	<489CE00F.3050500@acm.org>
	<4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
Message-Id: <5A11B757-A6A7-425C-B9A5-11E2F53A28D2@cisco.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Sun, 10 Aug 2008 18:08:04 -0700
X-Mailer: Apple Mail (2.928.1)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3158; t=1218416895;
	x=1219280895; c=relaxed/simple; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20Proposed=20resolutions=20for
	=20TURN=20open=20issues |Sender:=20;
	bh=WtOCbucsCXsGVLmjrja90YPACIzHOwJesSiUA9sNI6I=;
	b=NgYOh+q4jlyzMy9h9MLYxOzQbx53EaqF9bPXevxbFaZYDEXicmaAL30bYL
	KWzoJKTI45vxrwQEA8ohYDgwQcrX3Uw0IwQRmQzBTyrfIBMOuIJyXWobsH/J
	AWCHgURoE+;
Authentication-Results: sj-dkim-8; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim8002 verified; ); 
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


I prefer the simpler version without the steps 2-4 for a few reasons

1) it is simpler

2) it is what we agreed to in the meeting

3) it is more likely to actually get implemented

4) a client that cases can send a 0 length send request with this to  
see if it gets an error or not as soon as it likes


Cullen <with my individual hat on>


On Aug 8, 2008, at 6:10 PM, Philip Matthews wrote:

>
> On Fri, 8-Aug-08, at 20:08 , Marc Petit-Huguenin wrote:
>>>> if this is really required, I would suggest moving the attribute/ 
>>>> bit
>>>> to the allocate request instead. setting the DF-bit is normally  
>>>> done
>>>> when opening a socket (setsockopt IP_MTU_DISCOVER)
>>>
>>> Cullen Jennings, who was the person who pushed strongly for this
>>> feature, would like to set the DF bit on some packets but not  
>>> others.
>>>
>>
>> I also support this feature.
>
> After thinking about this feature a bit, and taking Alfred's comment  
> into account, it seems to me that there might be a platform where  
> this feature cannot be implemented with an unprivileged user-space  
> implementation. For example, a quick web search on how to do this  
> for MacOS seemed to indicate that there might be a problem. Without  
> getting into a discussion of which platforms can and cannot do it,  
> it seems wise to me to treat this as a feature which an  
> implementation might not be willing or able to support.
>
> Hence I have the following proposal for how to define this feature:
>
> 1) TURN would define a new attribute, call it SET-DF. The attribute  
> would have a value length of 0. The attribute would be in the  
> comprehension-required range.
>
> 2) A client MAY include the SET-DF option in an Allocate request.  
> Including this option means that the client is requesting an  
> allocation that supports this feature.
>
> 3) If the server cannot create an allocation that supports the  
> feature, the Allocate request is rejected with a 420 Unknown  
> Attributes and the UNKNOWN-ATTRIBUTES attribute would list this  
> attribute. [Note that in this case, the SET-DF attribute may not  
> really be unknown, but simply cannot be supported.]
>
> 4) If the server accepts the Allocate request, then the client MAY  
> use the SET-DF attribute in a Send request or a Send indication. If  
> the attribute is included, then the server sets the DF bit in the  
> corresponding UDP datagram towards the peer. If the attribute is not  
> included, the server does not set the DF bit.
>
> 5) Using the SET-DF attribute in a Send request or Send indication  
> on an allocation that does not support it causes the Send request to  
> be rejected and the Send indication to be silently ignored (=  
> standard behavior for a unknown comprehension-required attribute).
>
> An alternative to this would be to drop points (2) and (3), and say  
> that the server rejects a Send request if it cannot	 support the SET- 
> DF attribute. This is a bit simpler, but delays the point at which  
> the client discovers that the attribute is not supported.
>
> Comments?
>
> - Philip

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sun Aug 10 23:46:15 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD98E3A6C63;
	Sun, 10 Aug 2008 23:46:15 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2ED5A3A6819
	for <behave@core3.amsl.com>; Sun, 10 Aug 2008 23:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 X9qtx0UFWtw1 for <behave@core3.amsl.com>;
	Sun, 10 Aug 2008 23:46:13 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 133DD3A6BAE
	for <behave@ietf.org>; Sun, 10 Aug 2008 23:46:12 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m7B6jmF3026429 for <behave@ietf.org>; Mon, 11 Aug 2008 09:46:12 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 11 Aug 2008 09:45:47 +0300
Received: from esdhcp041147.research.nokia.com ([172.21.41.147]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 11 Aug 2008 09:45:46 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 11 Aug 2008 09:45:50 +0300
User-Agent: KMail/1.9.9
References: <214e01c8f8f6$50d10ce0$d35d150a@cisco.com>
In-Reply-To: <214e01c8f8f6$50d10ce0$d35d150a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808110945.50517.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 11 Aug 2008 06:45:46.0161 (UTC)
	FILETIME=[E2065A10:01C8FB7D]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] adopt draft-stewart-behave-sctpnat-04?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Friday 08 August 2008 04:30:17 ext Dan Wing, you wrote:
> The authors of "Stream Control Transmission Protocol (SCTP) Network Addre=
ss
> Translation" have asked their document
> <http://tools.ietf.org/html/draft-stewart-behave-sctpnat-04> to be adopted
> by Behave to meet the WG milestone for NATting SCTP.  As a reminder, their
> presentation from the Dublin meeting is at
> <http://www.ietf.org/proceedings/08jul/slides/behave-2.pdf>.
>
> Please send comments on adopting this document to the Behave list.

I'd support this.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug 11 00:09:14 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB9713A691E;
	Mon, 11 Aug 2008 00:09:14 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B9DF93A691E
	for <behave@core3.amsl.com>; Mon, 11 Aug 2008 00:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 DGiOndXYYMsg for <behave@core3.amsl.com>;
	Mon, 11 Aug 2008 00:09:13 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 0792C3A67ED
	for <behave@ietf.org>; Mon, 11 Aug 2008 00:09:12 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m7B76he6008655 for <behave@ietf.org>; Mon, 11 Aug 2008 02:08:52 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 11 Aug 2008 10:08:30 +0300
Received: from esdhcp041147.research.nokia.com ([172.21.41.147]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 11 Aug 2008 10:08:25 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 11 Aug 2008 10:08:30 +0300
User-Agent: KMail/1.9.9
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
	<489CE00F.3050500@acm.org>
	<4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
In-Reply-To: <4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808111008.30526.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 11 Aug 2008 07:08:26.0095 (UTC)
	FILETIME=[0C9BCFF0:01C8FB81]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Saturday 09 August 2008 04:10:58 ext Philip Matthews, you wrote:
> An alternative to this would be to drop points (2) and (3), and say
> that the server rejects a Send request if it cannot	 support the SET-
> DF attribute. This is a bit simpler, but delays the point at which the
> client discovers that the attribute is not supported.
>
> Comments?

What happens if SET-DF is *absent* and the OS does not support NOT setting =
the =

DF bit (from userland)? I recall BSDs, including OSX being in such situatio=
n.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug 11 04:50:23 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12EF33A6C7B;
	Mon, 11 Aug 2008 04:50:23 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7BEC03A6BBB
	for <behave@core3.amsl.com>; Mon, 11 Aug 2008 04:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.487
X-Spam-Level: 
X-Spam-Status: No, score=-0.487 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 1qrMcueV8C0f for <behave@core3.amsl.com>;
	Mon, 11 Aug 2008 04:50:17 -0700 (PDT)
Received: from s200aog11.obsmtp.com (s200aog11.obsmtp.com [207.126.144.125])
	by core3.amsl.com (Postfix) with SMTP id 6E8CB3A68FF
	for <behave@ietf.org>; Mon, 11 Aug 2008 04:50:16 -0700 (PDT)
Received: from source ([209.85.198.237]) by eu1sys200aob011.postini.com
	([207.126.147.11]) with SMTP; Mon, 11 Aug 2008 11:50:15 UTC
Received: by rv-out-0506.google.com with SMTP id g37so2169191rvb.23
	for <behave@ietf.org>; Mon, 11 Aug 2008 04:50:14 -0700 (PDT)
Received: by 10.140.134.15 with SMTP id h15mr3424067rvd.65.1218455414829;
	Mon, 11 Aug 2008 04:50:14 -0700 (PDT)
Received: by 10.141.186.2 with HTTP; Mon, 11 Aug 2008 04:50:14 -0700 (PDT)
Message-ID: <1879720d0808110450h1bbfe9cep9b1d6a389706716b@mail.gmail.com>
Date: Mon, 11 Aug 2008 12:50:14 +0100
From: "Benny Prijono" <bennylp@pjsip.org>
To: "Philip Matthews" <philip_matthews@magma.ca>
In-Reply-To: <7EC2DFA4-F444-425E-8478-FDA531322F45@magma.ca>
MIME-Version: 1.0
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
	<1879720d0807311438k3a90e41dm939dfb16fa047b31@mail.gmail.com>
	<7EC2DFA4-F444-425E-8478-FDA531322F45@magma.ca>
X-Google-Sender-Auth: 1df41ac72c727c9c
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1100660349=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

--===============1100660349==
Content-Type: multipart/alternative; 
	boundary="----=_Part_40391_20136755.1218455414826"

------=_Part_40391_20136755.1218455414826
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Fri, Aug 8, 2008 at 9:08 PM, Philip Matthews <philip_matthews@magma.ca>wrote:

>
> How about the following text? This is an attempt to give guidance while
> leaving the final decision of what to do up to the implementor.
>
> 10.3.  Receiving a ChannelBind Response
>
>    When the client receives a ChannelBind success response, it updates
>    its data structures to record that the channel binding is now active.
>
>    If the client receives a ChannelBind failure response that indicates
>    that the channel information is out-of-sync between the client and
>    the server (e.g., an unexpected 400 "Bad Request" response), then it
>    is RECOMMENDED that the client immediately delete the allocation and
>    start afresh with a new allocation.
>
>
I guess I'm okay with that. But we really want to handle out-of-sync
situation, can't we just add a new error code for this (e.g. 4xx Channel In
Use)?

This way the situation is more explicit, and client can also (ab)use it to
check if a specified channel is currently in use (i.e. by sending
ChannelBind and see if it receives 4xx Channel In Use response).

Cheers
 Benny

------=_Part_40391_20136755.1218455414826
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">On Fri, Aug 8, 2008 at 9:08 PM, Philip Matthews <span dir="ltr">&lt;<a href="mailto:philip_matthews@magma.ca">philip_matthews@magma.ca</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div><br><div>How about the following text? This is an attempt to give guidance while leaving the final decision of what to do up to the implementor.</div><div><br></div><div><div>10.3. &nbsp;Receiving a ChannelBind Response</div>
<div><br></div><div>&nbsp;&nbsp; When the client receives a ChannelBind success response, it updates</div><div>&nbsp;&nbsp; its data structures to record that the channel binding is now active.</div><div><br></div><div>&nbsp;&nbsp; If the client receives a ChannelBind failure response that indicates</div>
<div>&nbsp;&nbsp; that the channel information is out-of-sync between the client and</div><div>&nbsp;&nbsp; the server (e.g., an unexpected 400 &quot;Bad Request&quot; response), then it</div><div>&nbsp;&nbsp; is RECOMMENDED that the client immediately delete the allocation and</div>
<div>&nbsp;&nbsp; start afresh with a new allocation.</div><div><br></div></div><font color="#888888"><div></div></font></div></div></blockquote><div><br></div></div>I guess I&#39;m okay with that. But we really want to handle out-of-sync situation, can&#39;t we just add a new error code for this (e.g. 4xx Channel In Use)?<br>
<br>This way the situation is more explicit, and client can also (ab)use it to check if a specified channel is currently in use (i.e. by sending ChannelBind and see if it receives 4xx Channel In Use response).<br><br>Cheers<br>
&nbsp;Benny<br><br></div>

------=_Part_40391_20136755.1218455414826--

--===============1100660349==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

--===============1100660349==--


From behave-bounces@ietf.org  Tue Aug 12 18:57:01 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B3CDA3A69FB;
	Tue, 12 Aug 2008 18:57:01 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC5633A6BC1
	for <behave@core3.amsl.com>; Tue, 12 Aug 2008 18:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.469
X-Spam-Level: *
X-Spam-Status: No, score=1.469 tagged_above=-999 required=5 tests=[AWL=-1.409, 
	BAYES_05=-1.11, FRT_STOCK2=3.988]
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 tLJazPcJy2gr for <behave@core3.amsl.com>;
	Tue, 12 Aug 2008 18:57:00 -0700 (PDT)
Received: from mail-02.primus.ca (mail13.primus.ca [216.254.141.180])
	by core3.amsl.com (Postfix) with ESMTP id C56BD3A6A99
	for <behave@ietf.org>; Tue, 12 Aug 2008 18:56:59 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.2])
	by mail-02.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KT5be-00029W-0z; Tue, 12 Aug 2008 21:57:01 -0400
Message-Id: <E3470CF1-8F71-4EB7-8477-A6F3E4AA6E8A@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Marc Petit-Huguenin <petithug@acm.org>
In-Reply-To: <489D910D.7020009@acm.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 12 Aug 2008 21:56:35 -0400
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>	<48949422.4080103@db.org>
	<4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
	<489CE00F.3050500@acm.org>
	<4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
	<489D910D.7020009@acm.org>
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.2]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Sat, 9-Aug-08, at 08:43 , Marc Petit-Huguenin wrote:
> Philip Matthews wrote:
>>
>> On Fri, 8-Aug-08, at 20:08 , Marc Petit-Huguenin wrote:
>>>>> if this is really required, I would suggest moving the attribute/ 
>>>>> bit
>>>>> to the allocate request instead. setting the DF-bit is normally  
>>>>> done
>>>>> when opening a socket (setsockopt IP_MTU_DISCOVER)
>>>>
>>>> Cullen Jennings, who was the person who pushed strongly for this
>>>> feature, would like to set the DF bit on some packets but not  
>>>> others.
>>>>
>>>
>>> I also support this feature.
>>
>> After thinking about this feature a bit, and taking Alfred's comment
>> into account, it seems to me that there might be a platform where  
>> this
>> feature cannot be implemented with an unprivileged user-space
>> implementation. For example, a quick web search on how to do this for
>> MacOS seemed to indicate that there might be a problem. Without  
>> getting
>> into a discussion of which platforms can and cannot do it, it seems  
>> wise
>> to me to treat this as a feature which an implementation might not be
>> willing or able to support.
>>
>> Hence I have the following proposal for how to define this feature:
>>
>> 1) TURN would define a new attribute, call it SET-DF. The attribute
>> would have a value length of 0. The attribute would be in the
>> comprehension-required range.
>>
>> 2) A client MAY include the SET-DF option in an Allocate request.
>> Including this option means that the client is requesting an  
>> allocation
>> that supports this feature.
>>
>> 3) If the server cannot create an allocation that supports the  
>> feature,
>> the Allocate request is rejected with a 420 Unknown Attributes and  
>> the
>> UNKNOWN-ATTRIBUTES attribute would list this attribute. [Note that in
>> this case, the SET-DF attribute may not really be unknown, but simply
>> cannot be supported.]
>>
>> 4) If the server accepts the Allocate request, then the client MAY  
>> use
>> the SET-DF attribute in a Send request or a Send indication. If the
>> attribute is included, then the server sets the DF bit in the
>> corresponding UDP datagram towards the peer. If the attribute is not
>> included, the server does not set the DF bit.
>>
>> 5) Using the SET-DF attribute in a Send request or Send indication  
>> on an
>> allocation that does not support it causes the Send request to be
>> rejected and the Send indication to be silently ignored (= standard
>> behavior for a unknown comprehension-required attribute).
>>
>> An alternative to this would be to drop points (2) and (3), and say  
>> that
>> the server rejects a Send request if it cannot     support the SET-DF
>> attribute. This is a bit simpler, but delays the point at which the
>> client discovers that the attribute is not supported.
>>
>> Comments?
>
> Here's an alternate proposal:
>
> - Use bit 3 in REQUESTED-PROPS for the support of the DF bit.  This is
> consistent with the usage of REQUESTED-PROPS to query/request  
> allocation
> properties.

Perhaps I didn't make things clear in an earlier message.
Jonathan and I had a phone discussion about REQUESTED-PROPS. He argued  
(as Simon Perreault also argued) that using REQUESTED-PROPS as a set  
of bit flags meant that TURN had two different ways to define  
extensions (one by defining a new attribute and one using REQUESTED- 
PROPS) and he did not like this at all. He pushed very strongly for  
removing this use of REQUESTED-PROPS. Eventually, I agreed reluctantly  
to go along with this and remove this use REQUESTED-PROPS as part of  
the removal of Preserving allocations.
If the working group disagrees, we can put back in the use of  
REQUESTED-PROPS as a way to define new features, but for now it is out.

>
>
> - Redefine the reserved first 8 bits of PEER-ADDRESS to use bit 7 to
> carry the DF bit.  It can then be used in a Send indication/ 
> transaction
> and even in a ChannelBind transaction if one wants DF bit set in all
> packets.

We could do this (I had originally proposed something like this some  
time ago), but others objected saying that using a new attribute was  
cleaner and saving bytes was not important since the SET-DF attribute  
would only be used on certain special packets. Hence my proposal.

- Philip

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 13 05:45:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 033533A68C4;
	Wed, 13 Aug 2008 05:45:04 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A03D93A6B02
	for <behave@core3.amsl.com>; Wed, 13 Aug 2008 05:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.383
X-Spam-Level: 
X-Spam-Status: No, score=0.383 tagged_above=-999 required=5 tests=[AWL=0.382, 
	BAYES_50=0.001]
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 MFIBNV7wVDDi for <behave@core3.amsl.com>;
	Wed, 13 Aug 2008 05:45:00 -0700 (PDT)
Received: from mail-02.primus.ca (mail13.primus.ca [216.254.141.180])
	by core3.amsl.com (Postfix) with ESMTP id 5E6EE28C130
	for <behave@ietf.org>; Wed, 13 Aug 2008 05:41:59 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.2])
	by mail-02.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KTFey-0003qh-18; Wed, 13 Aug 2008 08:41:04 -0400
Message-Id: <2295C2E7-1EA0-49E2-803C-2B705D5B1474@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Jonathan Rosenberg <jdrosen@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 13 Aug 2008 08:39:55 -0400
X-Mailer: Apple Mail (2.919.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.2]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>
Subject: [BEHAVE] How to handle an unsupported class of a known STUN method?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

In section 7.3, draft-iet-behave-rfc3489bis-18 states that when a  
received STUN message with an unknown method is received, the message  
is silently discarded. However, it does not define how to handle a  
receive message with a known method when the class is unsupported; for  
example, an Allocate indication or a Data request, to give two  
examples from TURN.

I propose that this be clarified to say that the message is silently  
ignored in this case.

An alternative would be to silently ignore an unsupported indication,  
but to return 400 Bad Request for an unsupported request. However,  
this would mean that clients would have to be able to return error  
responses, and Rohan has previously objected to clients having to  
implement any sort of server-side processing.

- Philip

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 13 12:45:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CD973A6D01;
	Wed, 13 Aug 2008 12:45:49 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 944FD3A6CF1
	for <behave@core3.amsl.com>; Wed, 13 Aug 2008 12:45:48 -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 XWHRc1wvYXG7 for <behave@core3.amsl.com>;
	Wed, 13 Aug 2008 12:45:42 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 14ADA3A6D01
	for <behave@ietf.org>; Wed, 13 Aug 2008 12:45:39 -0700 (PDT)
Received: from [192.168.0.195] (static-167-138-7-89.ipcom.comunitel.net
	[89.7.138.167] (may be forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m7DJjN3L057714
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 13 Aug 2008 21:45:24 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <48A31A97.3060808@viagenie.ca>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Wed, 13 Aug 2008 21:45:18 +0200
References: <4897AFC0.9080007@gmail.com>	<475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
	<0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
	<48A31A97.3060808@viagenie.ca>
X-Mailer: Apple Mail (2.926)
Cc: behave@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>,
	Richard Nelson <richardn@cs.waikato.ac.nz>, int-area@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 13 aug 2008, at 19:32, Marc Blanchet wrote:

>>> Hm, it looks like the high water marks for TCP and UDP sessions  
>>> per subscriber (including non-active subscribers) is around 20 and  
>>> 40.
>>

>> ... the "planning for 500 connections per user" reference in the  
>> plenary presentation last week was way higher than I've heard  
>> previously,

> I think Miyakawa-san meant "up to 500", and he was referring to AJAX  
> connections used in applications such as google maps.

I would like to see some evidence for this. Google Maps only generates  
some 20 sessions for me.

Note that 500 ports per subscriber means only 125 subscribers per IPv4  
address, which means that we can't really afford endpoint independent  
mappings without limitations. We've had a short discussion on limiting  
endpoint independence to exclude stuff like HTTP in behave, but we  
haven't arrived at a useful conclusion yet.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 13 15:30:36 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E87453A6CA3;
	Wed, 13 Aug 2008 15:30:36 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 800D73A6A2F;
	Wed, 13 Aug 2008 15:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 dBmU5ti--bwa; Wed, 13 Aug 2008 15:30:34 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id B546A3A6CA3;
	Wed, 13 Aug 2008 15:30:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,203,1217808000"; d="scan'208";a="139712912"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 13 Aug 2008 22:30:34 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m7DMUYOi007677; 
	Wed, 13 Aug 2008 15:30:34 -0700
Received: from dwingwxp01 (dhcp-128-107-163-234.cisco.com [128.107.163.234])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m7DMUYTs004798;
	Wed, 13 Aug 2008 22:30:34 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Ted Lemon'" <Ted.Lemon@nominum.com>,
	"'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com><48A31A97.3060808@viagenie.ca><0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>
	<61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>
Date: Wed, 13 Aug 2008 15:30:34 -0700
Message-ID: <06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>
Thread-Index: Acj9fmydB20MtyCaQROlcUu54cZx8wAFQR1w
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1958; t=1218666634;
	x=1219530634; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Int-area]=20[BEHAVE]=20Inbound=20and=2
	0outbound=20connections |Sender:=20;
	bh=YEsdNp6SN5FnYrpu1eihhefUceuyB0VEewLXznLy4y0=;
	b=FzNlKwcxz+8cbZkSSGAKqwQjra1tCHnXHMMzNU5gP3XFQa+yP8odfw5fTS
	2hfUanU1pIT/8fEBBLtaPb/0mhdoKh6wdbHSZkCEioUlOt6Hwz+W6uPavWD4
	iSiQZoXoUw;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org, int-area@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 

> -----Original Message-----
> From: int-area-bounces@ietf.org 
> [mailto:int-area-bounces@ietf.org] On Behalf Of Ted Lemon
> Sent: Wednesday, August 13, 2008 12:54 PM
> To: Iljitsch van Beijnum
> Cc: int-area@ietf.org; behave@ietf.org
> Subject: Re: [Int-area] [BEHAVE] Inbound and outbound connections
> 
> On Aug 13, 2008, at 12:45 PM, Iljitsch van Beijnum wrote:
> > I would like to see some evidence for this. Google Maps 
> only generates
> > some 20 sessions for me.
> 
> Another problem with the statistic is that it assumes that all users  
> are surfing google web simultaneously.   In practice, use 
> tends to be  
> staggered.   As long as your NAT is noticing FIN and RST 
> packets, and  
> recycling ports quickly,

Caution needs to be exercised in recylcing TCP ports quickly;
see draft-ananth-tsvwg-timewait-00.txt and 
draft-ietf-tsvwg-port-randomization-01.txt.

> you can probably do just fine with 
> many more  
> subscribers per IP address than Miyakawa-san's worst-case scenario  
> would suggest.
> 
> That's all out the window if they're all doing P2P, of 
> course, because  
> those connections stay up longer.   But if we have IPv6 in the  
> network, we should really encourage people running P2P to use it,  
> because it should work better for them than IPv4 anyway - no NAT  
> traversal problems.

Without a way to accept incoming TCP sessions (e.g., UPnP or
some other way to ask for a publicly-routable transport address that
accepts incoming TCP SYNs), BitTorrent will consider p2p clients as 
leeches and download speeds will suffer:  keeping TCP connections
up even longer.  

We can't just 'encourage' p2p users to move to v6 until there is
content on v6 -- this is the very same problem for v6-only clients
wanting to access v6 content (there isn't any -- www.google.com,
www.cnn.com, www.amazon.com, are not on v6.  "ipv6.google.com" != 
"www.google.com").

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 13 15:46:28 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BEF23A6A32;
	Wed, 13 Aug 2008 15:46:28 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F7DC28C1A4
	for <behave@core3.amsl.com>; Wed, 13 Aug 2008 15:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 jFTSSex0JJRL for <behave@core3.amsl.com>;
	Wed, 13 Aug 2008 15:44:04 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id B435A3A6A35
	for <behave@ietf.org>; Wed, 13 Aug 2008 15:44:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,203,1217808000"; d="scan'208,217";a="75005572"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 13 Aug 2008 22:43:38 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m7DMhc2Y019129
	for <behave@ietf.org>; Wed, 13 Aug 2008 15:43:38 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m7DMhc93013739
	for <behave@ietf.org>; Wed, 13 Aug 2008 22:43:38 GMT
Received: from xmb-sjc-213.amer.cisco.com ([171.70.151.153]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Aug 2008 15:43:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 13 Aug 2008 15:43:37 -0700
Message-ID: <A6FB9D83DB5A7F4BB05AA6E6AA79A2E206EA1930@xmb-sjc-213.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Reason behind using interface's ipv4 address
thread-index: Acj9lgZbeKFVe7J8QNSFsoqflSaolQ==
From: "Nirav Shah (nirashah)" <nirashah@cisco.com>
To: <behave@ietf.org>
X-OriginalArrivalTime: 13 Aug 2008 22:43:38.0529 (UTC)
	FILETIME=[070D4110:01C8FD96]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4416; t=1218667418;
	x=1219531418; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=nirashah@cisco.com;
	z=From:=20=22Nirav=20Shah=20(nirashah)=22=20<nirashah@cisco.
	com>
	|Subject:=20Reason=20behind=20using=20interface's=20ipv4=20
	address |Sender:=20;
	bh=RXNOh/M4v6Qoa1CQR8hCTGKkBpPomg5ejn8TDaFzpSI=;
	b=LiqoqvQuEDcQNeao5m38fdMMyxrEbyCo1r0HOUQtNn2vBnvFRKNeP5S847
	49RY90Bu6zlj1SIqLnn2QCegMuGV7Q0RlH79c7g7sjFULV0lRzSIHqdZW4EJ
	EUB2+hQZb9;
Authentication-Results: sj-dkim-4; header.From=nirashah@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: [BEHAVE] Reason behind using interface's ipv4 address
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0803517553=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0803517553==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8FD96.07061A9C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8FD96.07061A9C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Experts,
=20
This is my first post to behave draft mailing list and not sure whether
the below question has been already asked before or not.
=20
I was going through the Behave draft and have few questions about the
same.
=20
    It is mentioned that in nat64, to translate the Ipv6 address to Ipv4
address, you required to use the interface's IPv4 address.
=20
   But, by doing this, aren't we limiting ourselves to only 64k flow
entries ? ( we can have more if we assign multiple ip address to same
interface)
=20
   In nat-pt we can assign the pool of ipv4 address, so we don't have
this limitation there.
=20
   Is there any particular reason behind not having the concept of using
pool for nat64 ?
=20
=20
Thanks,
Nirav Shah.
Software Engineer.
Cisco Systems.
=20
=20
=20
=20

------_=_NextPart_001_01C8FD96.07061A9C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3354" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>Hello=20
Experts,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>This =
is my first=20
post to behave draft mailing list and not sure whether the below =
question has=20
been already asked before or not.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>I was =
going through=20
the Behave draft and have few questions about the =
same.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D242233322-13082008>&nbsp;&nbsp;&nbsp;=20
It is mentioned that in nat64, to translate the Ipv6 address to Ipv4 =
address,=20
you required to use the interface's IPv4 address.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008>&nbsp;&nbsp;&nbsp;But, by doing this, aren't =
we=20
limiting ourselves to only 64k flow entries ?&nbsp;( we can have more if =
we=20
assign multiple ip address to same interface)</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D242233322-13082008>&nbsp;&nbsp; In=20
nat-pt we can assign the pool of ipv4 address, so we don't have this =
limitation=20
there.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D242233322-13082008>&nbsp;&nbsp; Is=20
there any particular reason behind&nbsp;not having&nbsp;the concept of =
using=20
pool for nat64&nbsp;?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>Nirav=20
Shah.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D242233322-13082008>Software=20
Engineer.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>Cisco=20
Systems.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C8FD96.07061A9C--

--===============0803517553==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

--===============0803517553==--


From behave-bounces@ietf.org  Wed Aug 13 16:03:13 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E2283A6B62;
	Wed, 13 Aug 2008 16:03:13 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A12F13A6B1A
	for <behave@core3.amsl.com>; Wed, 13 Aug 2008 16:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.498
X-Spam-Level: 
X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 dgvVtnMrp0kv for <behave@core3.amsl.com>;
	Wed, 13 Aug 2008 16:03:11 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 6D22D3A69AC
	for <behave@ietf.org>; Wed, 13 Aug 2008 16:03:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,204,1217808000"; 
	d="scan'208,217";a="139725016"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 13 Aug 2008 23:03:10 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m7DN3AFn012988
	for <behave@ietf.org>; Wed, 13 Aug 2008 16:03:10 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m7DN3APf025101
	for <behave@ietf.org>; Wed, 13 Aug 2008 23:03:10 GMT
Received: from xmb-sjc-213.amer.cisco.com ([171.70.151.153]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Aug 2008 16:03:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 13 Aug 2008 16:03:09 -0700
Message-ID: <A6FB9D83DB5A7F4BB05AA6E6AA79A2E206EA1957@xmb-sjc-213.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Reason behind using interface's ipv4 address
thread-index: Acj9mMC2tqNku8J9SDOyfcHL1K2GTw==
From: "Nirav Shah (nirashah)" <nirashah@cisco.com>
To: <behave@ietf.org>
X-OriginalArrivalTime: 13 Aug 2008 23:03:10.0261 (UTC)
	FILETIME=[C1755E50:01C8FD98]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4052; t=1218668590;
	x=1219532590; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=nirashah@cisco.com;
	z=From:=20=22Nirav=20Shah=20(nirashah)=22=20<nirashah@cisco.
	com>
	|Subject:=20Reason=20behind=20using=20interface's=20ipv4=20
	address |Sender:=20;
	bh=NfRVsE8tRTubMwA2WRWtepZdQU9djeaq2B+jqUXdEWE=;
	b=IH/kl6fqMPgaRN2/4KUdgS9H9BJyMVV8bSDuxM+TquCZD+AtHiGt36rB0g
	RznkGb6rdWOjN3DMmKLVfQtJpfzVT5TB1a8b2vhVHGum73USgiXdlxZqBW2e
	YbIfwifCUx;
Authentication-Results: sj-dkim-4; header.From=nirashah@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: [BEHAVE] Reason behind using interface's ipv4 address
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1662432017=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1662432017==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8FD98.C16FA112"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8FD98.C16FA112
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Experts,
=20
This is my first post to behave draft mailing list and not sure whether
the below question has been already asked before or not.
=20
I was going through the Behave draft and have few questions about the
same.
=20
    It is mentioned that in nat64, to translate the Ipv6 address to Ipv4
address, you required to use the interface's IPv4 address.
=20
   But, by doing this, aren't we limiting ourselves to only 64k flow
entries ? ( we can have more if we assign multiple ip address to same
interface)
=20
   In nat-pt we can assign the pool of ipv4 address, so we don't have
this limitation there.
=20
   Is there any particular reason behind not having the concept of using
pool for nat64 ?
=20
=20
Thanks,
Nirav Shah.
Software Engineer.
Cisco Systems.

------_=_NextPart_001_01C8FD98.C16FA112
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3354" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>Hello=20
Experts,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>This =
is my first=20
post to behave draft mailing list and not sure whether the below =
question has=20
been already asked before or not.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>I was =
going through=20
the Behave draft and have few questions about the =
same.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D242233322-13082008>&nbsp;&nbsp;&nbsp;=20
It is mentioned that in nat64, to translate the Ipv6 address to Ipv4 =
address,=20
you required to use the interface's IPv4 address.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008>&nbsp;&nbsp;&nbsp;But, by doing this, aren't =
we=20
limiting ourselves to only 64k flow entries ?&nbsp;( we can have more if =
we=20
assign multiple ip address to same interface)</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D242233322-13082008>&nbsp;&nbsp; In=20
nat-pt we can assign the pool of ipv4 address, so we don't have this =
limitation=20
there.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D242233322-13082008>&nbsp;&nbsp; Is=20
there any particular reason behind&nbsp;not having&nbsp;the concept of =
using=20
pool for nat64&nbsp;?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D242233322-13082008>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>Nirav=20
Shah.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D242233322-13082008>Software=20
Engineer.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D242233322-13082008>Cisco=20
Systems.</SPAN></FONT></DIV></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C8FD98.C16FA112--

--===============1662432017==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

--===============1662432017==--


From behave-bounces@ietf.org  Wed Aug 13 17:06:14 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA7B53A6D39;
	Wed, 13 Aug 2008 17:06:14 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE8F53A6D37;
	Wed, 13 Aug 2008 17:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 daaQ1YX-ppoB; Wed, 13 Aug 2008 17:06:12 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 8D2B83A6D36;
	Wed, 13 Aug 2008 17:06:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,204,1217808000"; d="scan'208";a="65253928"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 14 Aug 2008 00:06:05 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m7E065l5021182; 
	Wed, 13 Aug 2008 17:06:05 -0700
Received: from dwingwxp01 (dhcp-128-107-163-234.cisco.com [128.107.163.234])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m7E065iS010907;
	Thu, 14 Aug 2008 00:06:05 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Ted Lemon'" <Ted.Lemon@nominum.com>
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com><48A31A97.3060808@viagenie.ca><0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>
	<61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>
	<06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>
	<3700F03D-B959-45DA-907C-3E38A101EE5E@nominum.com>
Date: Wed, 13 Aug 2008 17:06:04 -0700
Message-ID: <078301c8fda1$8b4dc1b0$eaa36b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <3700F03D-B959-45DA-907C-3E38A101EE5E@nominum.com>
Thread-Index: Acj9mKcTAwLY/McFTdqFHjCa9AgCJAACIAFw
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=929; t=1218672365; x=1219536365;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Int-area]=20[BEHAVE]=20Inbound=20and=2
	0outbound=20connections |Sender:=20;
	bh=PgScz4VarNwFwfLg7aUlSJTryTlo62OTHcyAShh+lAA=;
	b=Qnk2u06vL2yomYhnH6geLMkFVJwfjS06ORgTK2L6LwxysxY7q22ssRnv/g
	5qieGe4zAPYVBp6XfsWo1Sx+NeDuJxQ08LWwAxXl3V7Unz1IvQ1wbil3Ddz3
	LXBy3EwUMLEEH/Xl9VM/R12rEyS2cKQJQvTFmwK1f9RYJwa5HJzlM=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org, int-area@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> On Aug 13, 2008, at 3:30 PM, Dan Wing wrote:
> > We can't just 'encourage' p2p users to move to v6 until there is
> > content on v6 -- this is the very same problem for v6-only clients
> > wanting to access v6 content (there isn't any -- www.google.com,
> > www.cnn.com, www.amazon.com, are not on v6.  "ipv6.google.com" !=
> > "www.google.com").
> 
> Actually, that's my point.   p2p is *not* cnn.com.   p2p can 
> discover  
> ipv6 peers automatically.   So okay, you can't get to 
> google.com with  
> v6.   But you can make your p2p stuff work better.   So there's some  
> value that ipv6 could add sooner rather than later.

Gotcha:  So you're saying "if you're behind a CGN (doing v4v4 NAT or
v6v4 NAT), you get 100 ports.  But if you are doing native v6, you
get 64K ports.  Your massive port-consuming p2p application will
work better with 64K ports".

Am I characterising that correctly?  

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 13 17:48:42 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3022C3A6A8C;
	Wed, 13 Aug 2008 17:48:42 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A5B93A6A8C;
	Wed, 13 Aug 2008 17:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
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 HoVnLKdLPY30; Wed, 13 Aug 2008 17:48:40 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id EB81E3A6A89;
	Wed, 13 Aug 2008 17:48:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,204,1217808000"; d="scan'208";a="41422030"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-5.cisco.com with ESMTP; 14 Aug 2008 00:48:44 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m7E0miUv017382; 
	Wed, 13 Aug 2008 17:48:44 -0700
Received: from dwingwxp01 (dhcp-128-107-163-234.cisco.com [128.107.163.234])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m7E0mi38016404;
	Thu, 14 Aug 2008 00:48:44 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Marc Blanchet'" <marc.blanchet@viagenie.ca>
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com><48A31A97.3060808@viagenie.ca><0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>	<61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>	<06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>	<3700F03D-B959-45DA-907C-3E38A101EE5E@nominum.com>	<078301c8fda1$8b4dc1b0$eaa36b80@cisco.com>
	<650302F0-80D0-4E8D-B887-4C976345A6B6@nominum.com>
	<48A37E92.8080707@viagenie.ca>
Date: Wed, 13 Aug 2008 17:48:43 -0700
Message-ID: <079a01c8fda7$80797b70$eaa36b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <48A37E92.8080707@viagenie.ca>
Thread-Index: Acj9pjLg+3ttEgZ1RWWg8Xrzxbg9yAAANq/A
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1018; t=1218674924;
	x=1219538924; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Int-area]=20[BEHAVE]=20Inbound=20and=2
	0outbound=20connections |Sender:=20;
	bh=CSCACr4UvT70nAd2d42bjHDY+2ZTdtld+ioXk1k1mK0=;
	b=TGin8A+kDXQg+YuhnaI5Q8nNhvsAo3idHard6+gb9L94/jkLMno55jWRWs
	XU0QpD2SsT6DelvnEbmflduuipLLJasiDUTbVOuitRcJ75G9H8HCBQQTDnPJ
	d9ApW5lMJQ;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: int-area@ietf.org, behave@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> Ted Lemon a =E9crit :
> > On Aug 13, 2008, at 5:06 PM, Dan Wing wrote:
> >> Gotcha:  So you're saying "if you're behind a CGN (doing =

> v4v4 NAT or
> >> v6v4 NAT), you get 100 ports.  But if you are doing native v6, you
> >> get 64K ports.  Your massive port-consuming p2p application will
> >> work better with 64K ports".
> >>
> >> Am I characterising that correctly?
> > =

> > Just about.   I was also making the additional point that =

> this provides =

> > a meaningful incentive to the end-user to go dual-stack.
> =

> and that with v6, you are not hidden by default (only by =

> firewall policy if desired), therefore it makes servers (ie. =

> a listening port) more easier to deploy. think about SIP today... =

> I've been involved in voipv6 and it is 10 times simpler =

> to deploy for that reason.

The filtering recommendations in =

http://tools.ietf.org/html/draft-ietf-v6ops-cpe-simple-security-03
would change your experience.  You might bring that up in v6ops.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 13 17:54:16 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5910A3A69C7;
	Wed, 13 Aug 2008 17:54:16 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B1B23A6D47
	for <behave@core3.amsl.com>; Wed, 13 Aug 2008 17:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 LiZdhd2K1xBF for <behave@core3.amsl.com>;
	Wed, 13 Aug 2008 17:54:14 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 424633A67A8
	for <behave@ietf.org>; Wed, 13 Aug 2008 17:54:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,204,1217808000"; 
	d="scan'208,217";a="139762594"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 14 Aug 2008 00:54:17 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m7E0sHCV014066
	for <behave@ietf.org>; Wed, 13 Aug 2008 17:54:17 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m7E0sHZW018956
	for <behave@ietf.org>; Thu, 14 Aug 2008 00:54:17 GMT
Received: from xmb-sjc-21d.amer.cisco.com ([171.70.151.140]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Aug 2008 17:54:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 13 Aug 2008 17:53:17 -0700
Message-ID: <F8EDCE19EA568B40BBAD7A4AF1DCC315077DDCFB@xmb-sjc-21d.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] Questions about IPV4 address pool
Thread-Index: Acj9qCN+wHD0LNJ2TdyzDSvTwuTCVA==
From: "Pooja Subramanya (posubram)" <posubram@cisco.com>
To: <behave@ietf.org>
X-OriginalArrivalTime: 14 Aug 2008 00:54:17.0546 (UTC)
	FILETIME=[477852A0:01C8FDA8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3769; t=1218675257;
	x=1219539257; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=posubram@cisco.com;
	z=From:=20=22Pooja=20Subramanya=20(posubram)=22=20<posubram@
	cisco.com>
	|Subject:=20[BEHAVE]=20Questions=20about=20IPV4=20address=2
	0pool |Sender:=20;
	bh=znSEn9RsUVGzrlIZ3CAH0HpcbetC8wEDcFSYd/QXv5M=;
	b=qnnEVjv7ZNnD4WBa06jmdUoTqRHmDcAbrJ+qB0yaSSjmXGweC6dsJZmolI
	wJvUBBgTwEJi6TVt6pXXHnhnC9tZAF8JDyZL4e1qBd3abSFcCb2ZjCEGPG/w
	Ga6wCzskAJT6am1ffUitAVyNSxv4Za/DAV+EJajBUZgzbuuE9NCHk=;
Authentication-Results: sj-dkim-1; header.From=posubram@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: [BEHAVE]  Questions about IPV4 address pool
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0473187675=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0473187675==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8FDA8.4766F56C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8FDA8.4766F56C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,=20
=20
I have a few questions about the Behave NAT64 draft.=20
=20
1. The draft mentions that the IPV4 address pool is nothing but the V4
address assigned to the NAT64 IPV4 interface. What does this mean ?
=20
a) Do we have only one IP address assigned to the NAT64 V4 interface?
And we can assign only that IP address to a V6 host?
b) Can a NAT64 V4 interface be assigned more than one IPV4 address?=20
=20
=20
2. Can a NAT64 have more than one IPV4 interface? Are there any
restrictions to this? Does this mean that we cannot have a mixed cloud
of networks? For ex: is it possible to have a V6 interface as the inside
network of NAT64 and also have a V6 and a couple of V4 networks on the
outside interface?=20
=20
Thanks in advance for the help.=20
=20
Regards,=20
Pooja
=20

------_=_NextPart_001_01C8FDA8.4766F56C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16674" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D921452922-13082008>Hi,=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D921452922-13082008>I have =
a few=20
questions about the Behave NAT64 draft. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D921452922-13082008>1. The =
draft=20
mentions that the IPV4 address pool is nothing but the V4 address =
assigned to=20
the NAT64 IPV4 interface. What does this mean ?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D921452922-13082008>a)&nbsp;Do we have=20
only one IP address assigned to the NAT64 V4 interface?&nbsp; And we can =
assign=20
only that IP address to a V6 host?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D921452922-13082008>b) Can =
a NAT64 V4=20
interface be assigned more than one IPV4 address? </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D921452922-13082008>2.&nbsp;Can a NAT64=20
have more than one IPV4 interface? Are there any restrictions to this? =
Does this=20
mean that we cannot have a mixed cloud of networks? For ex: is it =
possible to=20
have a V6 interface as the inside network of NAT64 and also have a V6 =
and a=20
couple of V4 networks on the outside interface? </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D921452922-13082008>Thanks =
in advance=20
for the help. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D921452922-13082008>Regards,=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008>Pooja</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D921452922-13082008></SPAN></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C8FDA8.4766F56C--

--===============0473187675==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

--===============0473187675==--


From behave-bounces@ietf.org  Wed Aug 13 23:08:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F00D13A6AAA;
	Wed, 13 Aug 2008 23:08:48 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB2DA3A6A5A
	for <behave@core3.amsl.com>; Wed, 13 Aug 2008 23:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 jIvGheHgF0Px for <behave@core3.amsl.com>;
	Wed, 13 Aug 2008 23:08:47 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 2B4C63A6A3E
	for <behave@ietf.org>; Wed, 13 Aug 2008 23:08:46 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m7E67fef008389; Thu, 14 Aug 2008 01:08:41 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 14 Aug 2008 09:08:17 +0300
Received: from esdhcp04338.research.nokia.com ([172.21.43.38]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 14 Aug 2008 09:08:15 +0300
From: =?utf-8?q?R=C3=A9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org
Date: Thu, 14 Aug 2008 09:08:21 +0300
User-Agent: KMail/1.9.9
References: <A6FB9D83DB5A7F4BB05AA6E6AA79A2E206EA1930@xmb-sjc-213.amer.cisco.com>
In-Reply-To: <A6FB9D83DB5A7F4BB05AA6E6AA79A2E206EA1930@xmb-sjc-213.amer.cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808140908.22074.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 14 Aug 2008 06:08:15.0208 (UTC)
	FILETIME=[23976E80:01C8FDD4]
X-Nokia-AV: Clean
Cc: "ext Nirav Shah \(nirashah\)" <nirashah@cisco.com>
Subject: Re: [BEHAVE] Reason behind using interface's ipv4 address
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

T24gVGh1cnNkYXkgMTQgQXVndXN0IDIwMDggMDE6NDM6MzcgZXh0IE5pcmF2IFNoYWggKG5pcmFz
aGFoKSwgeW91IHdyb3RlOgo+ICAgIEJ1dCwgYnkgZG9pbmcgdGhpcywgYXJlbid0IHdlIGxpbWl0
aW5nIG91cnNlbHZlcyB0byBvbmx5IDY0ayBmbG93Cj4gZW50cmllcyA/ICggd2UgY2FuIGhhdmUg
bW9yZSBpZiB3ZSBhc3NpZ24gbXVsdGlwbGUgaXAgYWRkcmVzcyB0byBzYW1lCj4gaW50ZXJmYWNl
KQoKTm8uIFlvdSBjYW4gaGF2ZSBtdWx0aXBsZSBJUHY0IGFkZHJlc3NlcyBhc3NpZ25lZCB0byB0
aGUgTkFUNjQgYm94LiBIb3dldmVyLCAKeW91IG11c3QgYWx3YXlzIG1hcCBhIGdpdmVuIElQdjYg
Y2xpZW50IHRvIHRoZSBzYW1lIElQdjQgYWRkcmVzcyAtIG90aGVyd2lzZSAKZXZlcnkgc2Vjb25k
IHdlYiBhcHBsaWNhdGlvbnMgYW5kIG1hbnkgcHJvdG9jb2xzIHdpbGwgYnJlYWsuCgpJbiBhbnkg
Y2FzZSwgaXQgaXMgYXNzdW1lZCB0aGF0IElQdjQgaXMgYSByZXN0cmljdGVkIHJlc291cmNlIGlm
IHlvdSBuZWVkIApOQVQ2NC4gT3RoZXJ3aXNlLCB1c2luZyBOQVQtbGVzcyBkdWFsLXN0YWNrIHdv
dWxkIGJlIGEgbG90IGJldHRlci4KCi0tIApSw6ltaSBEZW5pcy1Db3VybW9udApNYWVtbyBTb2Z0
d2FyZSwgTm9raWEgRGV2aWNlcyBSJkQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18KQmVoYXZlIG1haWxpbmcgbGlzdApCZWhhdmVAaWV0Zi5vcmcKaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9iZWhhdmUK


From behave-bounces@ietf.org  Thu Aug 14 02:53:21 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FE843A6C28;
	Thu, 14 Aug 2008 02:53:21 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F0B653A6C11
	for <behave@core3.amsl.com>; Thu, 14 Aug 2008 02:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 Pn-v-r2SBhA1 for <behave@core3.amsl.com>;
	Thu, 14 Aug 2008 02:53:17 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 268D93A6BA4
	for <behave@ietf.org>; Thu, 14 Aug 2008 02:53:16 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m7E9rF69070092
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 14 Aug 2008 11:53:16 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <D06053CE-6F19-45F0-BFFC-5409EDFA2B94@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Nirav Shah (nirashah) <nirashah@cisco.com>
In-Reply-To: <A6FB9D83DB5A7F4BB05AA6E6AA79A2E206EA1957@xmb-sjc-213.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 14 Aug 2008 11:53:14 +0200
References: <A6FB9D83DB5A7F4BB05AA6E6AA79A2E206EA1957@xmb-sjc-213.amer.cisco.com>
X-Mailer: Apple Mail (2.926)
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Reason behind using interface's ipv4 address
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 14 aug 2008, at 1:03, Nirav Shah (nirashah) wrote:

>     It is mentioned that in nat64, to translate the Ipv6 address to  =

> Ipv4 address, you required to use the interface's IPv4 address.

>     But, by doing this, aren't we limiting ourselves to only 64k  =

> flow entries ? ( we can have more if we assign multiple ip address  =

> to same interface)

Is there any specific text that requires this limitation?

If so, it should probably be updated. A pool would be appropriate,  =

assuming the considerations mentioned by R=E9mi.

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 14 03:02:10 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D82233A6C66;
	Thu, 14 Aug 2008 03:02:10 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A9643A6B2E;
	Thu, 14 Aug 2008 03:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 T2Chy1lkCtjn; Thu, 14 Aug 2008 03:02:08 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 09A223A68F3;
	Thu, 14 Aug 2008 03:02:07 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m7EA1tlp070245
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 14 Aug 2008 12:01:56 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <530D1A99-6649-4432-A7EC-38368732CCCB@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 14 Aug 2008 12:01:56 +0200
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com><48A31A97.3060808@viagenie.ca><0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>
	<61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>
	<06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>
X-Mailer: Apple Mail (2.926)
Cc: behave@ietf.org, int-area@ietf.org, 'Ted Lemon' <Ted.Lemon@nominum.com>
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 14 aug 2008, at 0:30, Dan Wing wrote:

> We can't just 'encourage' p2p users to move to v6 until there is
> content on v6 -- this is the very same problem for v6-only clients
> wanting to access v6 content (there isn't any -- www.google.com,
> www.cnn.com, www.amazon.com, are not on v6.  "ipv6.google.com" !=
> "www.google.com").

Actually I'm downloading a file with BitTorrent right now, and I'm  
connected to 133 peers, 131 IPv4 and 2 IPv6 (6to4, but still). The  
current trackers and clients usually won't let you do IPv6, but the  
DHT that's in Azureus and some other clients will exchange IPv6  
addresses as well as IPv4 addresses, so users of clients that support  
DHT and IPv6 running on systems with IPv6 connectivity will  
automatically make use of IPv6.

Note that for the purpose of IPv4->IPv6 transition there are two types  
of peer-to-peer: the BitTorrent type, where an individual peer doesn't  
need to be able to talk to _all_ other peers, but just to a large  
enough subset to get the download going.

The other type is VoIP, where there is the requirement that all peers  
can (potentially) talk to all other peers.

The BitTorrent type doens't need NAT64 but just a small set of dual  
stack peers that connect the IPv4 and IPv6 clouds. The VoIP type needs  
a solution like NAT64 to make the IPv6 transition.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 14 03:40:31 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4D5B3A6C4E;
	Thu, 14 Aug 2008 03:40:31 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 690C13A6C4E
	for <behave@core3.amsl.com>; Thu, 14 Aug 2008 03:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.485
X-Spam-Level: *
X-Spam-Status: No, score=1.485 tagged_above=-999 required=5 tests=[AWL=0.581, 
	BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,
	RELAY_IS_203=0.994]
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 Lmnwe7DbIuhi for <behave@core3.amsl.com>;
	Thu, 14 Aug 2008 03:40:29 -0700 (PDT)
Received: from zns001-0m9002.yokogawa.co.jp (zns001-0m9002.yokogawa.co.jp
	[203.174.79.139])
	by core3.amsl.com (Postfix) with ESMTP id 3FB3F3A6B2C
	for <behave@ietf.org>; Thu, 14 Aug 2008 03:40:29 -0700 (PDT)
Received: from zns001-0m9002.yokogawa.co.jp (localhost [127.0.0.1])
	by zns001-0m9002.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	m7EAe9DF026049; Thu, 14 Aug 2008 19:40:09 +0900 (JST)
Received: from zex001-0m9027.jp.ykgw.net (zex001-0m9027.jp.ykgw.net
	[10.0.11.46])
	by zns001-0m9002.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	m7EAe8rh026044; Thu, 14 Aug 2008 19:40:08 +0900 (JST)
Received: from EXMAIL03.jp.ykgw.net ([10.0.11.29]) by
	zex001-0m9027.jp.ykgw.net ([10.0.11.46]) with mapi;
	Thu, 14 Aug 2008 19:40:08 +0900
From: <Masahito.Endou@jp.yokogawa.com>
To: <brian.e.carpenter@gmail.com>, <v6ops@ops.ietf.org>
Date: Thu, 14 Aug 2008 19:40:06 +0900
Thread-Topic: I-D Action:draft-endo-v6ops-dnsproxy-00.txt
Thread-Index: Acj9maLKsSWqMsLGTBSsAu8Ux7q5oAAWP0lA
Message-ID: <B76F972AA81DDB4F8E4BA80DEDE43983D32CEBBA29@EXMAIL03.jp.ykgw.net>
In-Reply-To: <48A3698E.1000209@gmail.com>
Accept-Language: ja-JP
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: ja-JP
MIME-Version: 1.0
Cc: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-endo-v6ops-dnsproxy-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi, Brian

Thanks for your comments.

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> Sent: Thursday, August 14, 2008 8:09 AM
> To: IPv6 Operations
> Subject: Re: I-D Action:draft-endo-v6ops-dnsproxy-00.txt
>
> Hi,
>
> I have a couple of comments on this, and a question.
>
> > 3.2.  IPv4 Address Pool
> >
> >    IPv4 Address Pool stores IPv4 addresses that are assigned to each
> >    translator.  DNS Proxy selects an IPv4 address from it,
> and DNS Proxy
> >    maps an IPv6 address to selected IPv4 address.
> >
> >    The entry of this pool MUST have following information.
> >
> >
> >          IPv4 Address:
> >            This IPv4 address is used to map to an IPv6 address.
> >
> >          Address Status:
> >            This information indicates a status of this IPv4 address.
> >            The status has two condition "Un-Mapped" and
> "Mapped".  If
> >            Un-mapped status, DNS Proxy can select this entry to map.
> >            Otherwise DNS Proxy cannot do it.
> >
> >            Un-mapped:
> >              This IPv4 address is not mapped.
> >            Mapped:
> >              This IPv4 address is already mapped.
>
> If I understand this correctly, it means that the proposal
> only allows exactly one IPv6 address to be mapped to one IPv4 address.
> Since any deployment scenario I can imagine will have a
> shortage of IPv4 addresses, it seems to me essential to
> support IPv4 address sharing and port mapping.

This IPv4 address pool is only used by translating from IPv4 to IPv6.
DNS proxy can only know IPv4 destination address that a client will communicate to.
In this case, to support IPv4 address sharing, DNS proxy must know a destination port number.
It requires relationship with DNS proxy and clients. I think that it is not reasonable.

In specific area like company or campus networks, this proposal will be effective,
because DNS proxy use IPv4 private addresses.

> > 7.  Security Considerations
> >
> >    TBD
>
> You don't discuss DNSSEC, which is an essential issue for the
> future. I don't think we can propose a solution without
> DNSSEC support.

I agreed with you.
I should consider about DNSSEC.

> My question is, why not combine this draft with the DNS64
> model in draft-bagnulo-behave-nat64?

Sorry, I didn't read this proposal yet.
I will check soon.

// masaxmasa

>
>     Brian
>
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 14 07:45:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4CD4E3A6C60;
	Thu, 14 Aug 2008 07:45:50 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A8BEA3A6824;
	Thu, 14 Aug 2008 07:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.314
X-Spam-Level: 
X-Spam-Status: No, score=-5.314 tagged_above=-999 required=5
	tests=[AWL=-0.782, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	RCVD_NUMERIC_HELO=2.067]
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 Cf4NtM36d5Y4; Thu, 14 Aug 2008 07:45:48 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 8C3653A6A48;
	Thu, 14 Aug 2008 07:45:48 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m7EEjal6003056; Thu, 14 Aug 2008 09:45:40 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 14 Aug 2008 17:45:35 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 14 Aug 2008 17:45:29 +0300
Received: from 143.2.223.10.in-addr.arpa ([10.241.184.208]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.3959); Thu, 14 Aug 2008 17:45:29 +0300
Message-Id: <41967D62-5702-4BC2-AB13-96E64672E768@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 14 Aug 2008 07:45:24 -0700
References: <4897AFC0.9080007@gmail.com>
	<475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 14 Aug 2008 14:45:29.0360 (UTC)
	FILETIME=[65633900:01C8FE1C]
X-Nokia-AV: Clean
Cc: int-area@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>,
	Richard Nelson <richardn@cs.waikato.ac.nz>, behave@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 2008-8-5, at 2:40, ext Iljitsch van Beijnum wrote:
> Hm, it looks like the high water marks for TCP and UDP sessions per  
> subscriber (including non-active subscribers) is around 20 and 40.


http://www.wand.net.nz/~salcock/someisp/flow_counting/result_page.html

The graph you commented on talks about "peak sessions per subscriber  
(mean)", and if I understand the text correctly, that means dividing  
all active sessions by all active subscribers at the time. It's not  
actually a per-user measure.

If you scroll down on that page, the "peak tcp session per active  
subscriber (percentiles)" graph shows you how heavy-tailed the  
underlying distribution is - 5% of users have more than 100  
connections active, and 1% between 500-1000. If a CGN enforced a limit  
of 100 connections, an ISP would get calls from 5% of his customers -  
probably not what they'd like to see happen.

(These are interesting numbers, by the way - I wish other ISPs could  
share similar data!)

Lars
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 14 13:09:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 83A9F3A6868;
	Thu, 14 Aug 2008 13:09:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C0D73A698F;
	Wed, 13 Aug 2008 10:32:44 -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 OTsWVQYzFMOE; Wed, 13 Aug 2008 10:32:43 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id E788B3A67A8;
	Wed, 13 Aug 2008 10:32:42 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id 5045229E14D9; Wed, 13 Aug 2008 13:32:08 -0400 (EDT)
Received: from Macintosh-7.local (unknown [206.167.141.86])
	by jazz.viagenie.ca (Postfix) with ESMTP id E733329E1433;
	Wed, 13 Aug 2008 13:32:07 -0400 (EDT)
Message-ID: <48A31A97.3060808@viagenie.ca>
Date: Wed, 13 Aug 2008 13:32:07 -0400
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: Spencer Dawkins <spencer@wonderhamster.org>
References: <4897AFC0.9080007@gmail.com>	<475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
	<0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
In-Reply-To: <0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
X-Mailman-Approved-At: Thu, 14 Aug 2008 13:09:38 -0700
Cc: behave@ietf.org, Shane Alcock <salcock@cs.waikato.ac.nz>,
	Richard Nelson <richardn@cs.waikato.ac.nz>, int-area@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Spencer Dawkins a =E9crit :
> Agreeing with Iljitch's math here, but ...
> =

>>> In case people aren't already aware of it, I think the work at the
>>> second URL below is very interesting in discussing the possible
>>> implications of CGN, and in particular the number of outbound and
>>> inbound ports needed per active host.
>>
>> Hm, it looks like the high water marks for TCP and UDP sessions per =

>> subscriber (including non-active subscribers) is around 20 and 40.
>>
>> For our purposes we can probably assume that the UDP is lower than TCP =

>> because UDP in this is very likely mostly DNS which shouldn't have to  =

>> go through a NAT64.
>>
>> So that means a single IPv4 address can support about 3000 subscribers.
> =

> ... the "planning for 500 connections per user" reference in the plenary =

> presentation last week was way higher than I've heard previously, but =

> the working number from the P2PI workshop in May was about 80 for =

> BitTorrent,

I think Miyakawa-san meant "up to 500", and he was referring to AJAX =

connections used in applications such as google maps.

if the deployment scenario is based on multiple computers behind a NAT =

in the home, and 200 connections per computer and a few people in the =

home accessing Internet services, given that even now the TiVO and other =

boxes are accessing Youtube and other services, then I think 500 is a =

good cap number since it will happen over time. We shall need to take =

this number as a reference point for our work.

Marc.


> wasn't it? So we're already looking at a factor-of-two =

> reduction in what we can support on one IPv4 address, before someone =

> comes up with an even cuter connection-use strategy...
> =

> :-(
> =

> Spencer
> =

> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 14 13:09:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B37323A692D;
	Thu, 14 Aug 2008 13:09:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D9A8E28C194;
	Wed, 13 Aug 2008 12:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.408
X-Spam-Level: 
X-Spam-Status: No, score=-6.408 tagged_above=-999 required=5 tests=[AWL=0.191, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 y4k0hkxEbGY3; Wed, 13 Aug 2008 12:54:22 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163])
	by core3.amsl.com (Postfix) with ESMTP id DD2793A6C64;
	Wed, 13 Aug 2008 12:54:19 -0700 (PDT)
Received: from source ([64.89.228.228]) (using TLSv1) by
	exprod7ob105.postini.com ([64.18.6.12]) with SMTP; 
	Wed, 13 Aug 2008 12:54:16 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client CN "webmail.nominum.com",
	Issuer "Go Daddy Secure Certification Authority" (verified OK))
	by shell-ng.nominum.com (Postfix) with ESMTP id 9C12F1A8201;
	Wed, 13 Aug 2008 12:54:16 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.0.252] (66.93.162.128) by exchange-01.win.nominum.com
	(64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.278.0;
	Wed, 13 Aug 2008 12:54:16 -0700
Message-ID: <61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>
MIME-Version: 1.0 (Apple Message framework v928.1)
Date: Wed, 13 Aug 2008 12:54:14 -0700
References: <4897AFC0.9080007@gmail.com>
	<475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com>
	<0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com>
	<48A31A97.3060808@viagenie.ca>
	<0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>
X-Mailer: Apple Mail (2.928.1)
X-Mailman-Approved-At: Thu, 14 Aug 2008 13:09:38 -0700
Cc: int-area@ietf.org, behave@ietf.org
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Aug 13, 2008, at 12:45 PM, Iljitsch van Beijnum wrote:
> I would like to see some evidence for this. Google Maps only generates
> some 20 sessions for me.

Another problem with the statistic is that it assumes that all users  
are surfing google web simultaneously.   In practice, use tends to be  
staggered.   As long as your NAT is noticing FIN and RST packets, and  
recycling ports quickly, you can probably do just fine with many more  
subscribers per IP address than Miyakawa-san's worst-case scenario  
would suggest.

That's all out the window if they're all doing P2P, of course, because  
those connections stay up longer.   But if we have IPv6 in the  
network, we should really encourage people running P2P to use it,  
because it should work better for them than IPv4 anyway - no NAT  
traversal problems.

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 14 13:09:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E15433A6953;
	Thu, 14 Aug 2008 13:09:40 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A7C13A69AE;
	Wed, 13 Aug 2008 16:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.424
X-Spam-Level: 
X-Spam-Status: No, score=-6.424 tagged_above=-999 required=5 tests=[AWL=0.175, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 CwXSZKHugdGL; Wed, 13 Aug 2008 16:02:20 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7ob115.obsmtp.com [64.18.2.216])
	by core3.amsl.com (Postfix) with ESMTP id 49D393A6874;
	Wed, 13 Aug 2008 16:02:18 -0700 (PDT)
Received: from source ([64.89.228.228]) (using TLSv1) by
	exprod7ob115.postini.com ([64.18.6.12]) with SMTP; 
	Wed, 13 Aug 2008 16:02:21 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client CN "webmail.nominum.com",
	Issuer "Go Daddy Secure Certification Authority" (verified OK))
	by shell-ng.nominum.com (Postfix) with ESMTP id A94AC1A8201;
	Wed, 13 Aug 2008 16:02:21 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.0.252] (66.93.162.128) by exchange-01.win.nominum.com
	(64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.278.0;
	Wed, 13 Aug 2008 16:02:21 -0700
Message-ID: <3700F03D-B959-45DA-907C-3E38A101EE5E@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>
MIME-Version: 1.0 (Apple Message framework v928.1)
Date: Wed, 13 Aug 2008 16:02:19 -0700
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com><48A31A97.3060808@viagenie.ca><0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>
	<61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>
	<06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>
X-Mailer: Apple Mail (2.928.1)
X-Mailman-Approved-At: Thu, 14 Aug 2008 13:09:38 -0700
Cc: "behave@ietf.org" <behave@ietf.org>,
	"int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Aug 13, 2008, at 3:30 PM, Dan Wing wrote:
> We can't just 'encourage' p2p users to move to v6 until there is
> content on v6 -- this is the very same problem for v6-only clients
> wanting to access v6 content (there isn't any -- www.google.com,
> www.cnn.com, www.amazon.com, are not on v6.  "ipv6.google.com" !=
> "www.google.com").

Actually, that's my point.   p2p is *not* cnn.com.   p2p can discover  
ipv6 peers automatically.   So okay, you can't get to google.com with  
v6.   But you can make your p2p stuff work better.   So there's some  
value that ipv6 could add sooner rather than later.

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 14 13:09:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1444D3A6996;
	Thu, 14 Aug 2008 13:09:41 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8985F3A6A36;
	Wed, 13 Aug 2008 17:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.437
X-Spam-Level: 
X-Spam-Status: No, score=-6.437 tagged_above=-999 required=5 tests=[AWL=0.162, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bt-T983MhWxN; Wed, 13 Aug 2008 17:27:44 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161])
	by core3.amsl.com (Postfix) with ESMTP id 90C5D3A67A8;
	Wed, 13 Aug 2008 17:27:42 -0700 (PDT)
Received: from source ([64.89.228.228]) (using TLSv1) by
	exprod7ob104.postini.com ([64.18.6.12]) with SMTP; 
	Wed, 13 Aug 2008 17:27:39 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(Client CN "webmail.nominum.com",
	Issuer "Go Daddy Secure Certification Authority" (verified OK))
	by shell-ng.nominum.com (Postfix) with ESMTP id 2C1DD1A8201;
	Wed, 13 Aug 2008 17:27:39 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.0.252] (66.93.162.128) by exchange-01.win.nominum.com
	(64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.278.0;
	Wed, 13 Aug 2008 17:27:38 -0700
Message-ID: <650302F0-80D0-4E8D-B887-4C976345A6B6@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <078301c8fda1$8b4dc1b0$eaa36b80@cisco.com>
MIME-Version: 1.0 (Apple Message framework v928.1)
Date: Wed, 13 Aug 2008 17:27:37 -0700
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com><48A31A97.3060808@viagenie.ca><0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>
	<61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>
	<06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>
	<3700F03D-B959-45DA-907C-3E38A101EE5E@nominum.com>
	<078301c8fda1$8b4dc1b0$eaa36b80@cisco.com>
X-Mailer: Apple Mail (2.928.1)
X-Mailman-Approved-At: Thu, 14 Aug 2008 13:09:38 -0700
Cc: "behave@ietf.org" <behave@ietf.org>,
	"int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Aug 13, 2008, at 5:06 PM, Dan Wing wrote:
> Gotcha:  So you're saying "if you're behind a CGN (doing v4v4 NAT or
> v6v4 NAT), you get 100 ports.  But if you are doing native v6, you
> get 64K ports.  Your massive port-consuming p2p application will
> work better with 64K ports".
>
> Am I characterising that correctly?

Just about.   I was also making the additional point that this  
provides a meaningful incentive to the end-user to go dual-stack.

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 14 13:09:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41E443A69D8;
	Thu, 14 Aug 2008 13:09:41 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE3CC3A6A89;
	Wed, 13 Aug 2008 17:39:09 -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 8lwF8HbvmuBB; Wed, 13 Aug 2008 17:39:09 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 17CDD3A69C7;
	Wed, 13 Aug 2008 17:39:09 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id 064B614A0005; Wed, 13 Aug 2008 20:38:43 -0400 (EDT)
Received: from Macintosh-7.local (unknown [65.38.93.2])
	by jazz.viagenie.ca (Postfix) with ESMTP id C3E0429E1433;
	Wed, 13 Aug 2008 20:38:42 -0400 (EDT)
Message-ID: <48A37E92.8080707@viagenie.ca>
Date: Wed, 13 Aug 2008 20:38:42 -0400
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <4897AFC0.9080007@gmail.com><475FAF68-B434-418B-B371-5FD3A3A384A3@muada.com><0a5101c8f6fb$1f808640$6501a8c0@china.huawei.com><48A31A97.3060808@viagenie.ca><0E059CE1-4E21-4183-B994-C9AC828AF253@muada.com>	<61A2447C-269A-4FA4-AC36-6C735D0EDCCF@nominum.com>	<06ae01c8fd94$338e9ab0$eaa36b80@cisco.com>	<3700F03D-B959-45DA-907C-3E38A101EE5E@nominum.com>	<078301c8fda1$8b4dc1b0$eaa36b80@cisco.com>
	<650302F0-80D0-4E8D-B887-4C976345A6B6@nominum.com>
In-Reply-To: <650302F0-80D0-4E8D-B887-4C976345A6B6@nominum.com>
X-Mailman-Approved-At: Thu, 14 Aug 2008 13:09:38 -0700
Cc: "int-area@ietf.org" <int-area@ietf.org>,
	"behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] [Int-area]  Inbound and outbound connections
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Ted Lemon a =E9crit :
> On Aug 13, 2008, at 5:06 PM, Dan Wing wrote:
>> Gotcha:  So you're saying "if you're behind a CGN (doing v4v4 NAT or
>> v6v4 NAT), you get 100 ports.  But if you are doing native v6, you
>> get 64K ports.  Your massive port-consuming p2p application will
>> work better with 64K ports".
>>
>> Am I characterising that correctly?
> =

> Just about.   I was also making the additional point that this provides =

> a meaningful incentive to the end-user to go dual-stack.

and that with v6, you are not hidden by default (only by firewall policy =

if desired), therefore it makes servers (ie. a listening port) more =

easier to deploy. think about SIP today... I've been involved in voipv6 =

and it is 10 times simpler to deploy for that reason.

Marc.

> =

> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug 15 13:17:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 88F703A6A68;
	Fri, 15 Aug 2008 13:17:12 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15E563A6A68
	for <behave@core3.amsl.com>; Fri, 15 Aug 2008 13:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.993
X-Spam-Level: 
X-Spam-Status: No, score=-0.993 tagged_above=-999 required=5 tests=[AWL=1.605, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 aucgkGTk64ZQ for <behave@core3.amsl.com>;
	Fri, 15 Aug 2008 13:17:11 -0700 (PDT)
Received: from mail-09.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 072013A69FA
	for <behave@ietf.org>; Fri, 15 Aug 2008 13:17:10 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.2])
	by mail-09.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KU5jX-0001oF-24; Fri, 15 Aug 2008 16:17:15 -0400
Message-Id: <FA7C71CC-6BA9-40F8-BE65-AD6D52866DC8@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Benny Prijono <bennylp@pjsip.org>
In-Reply-To: <1879720d0808110450h1bbfe9cep9b1d6a389706716b@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 15 Aug 2008 14:18:16 -0400
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
	<1879720d0807311438k3a90e41dm939dfb16fa047b31@mail.gmail.com>
	<7EC2DFA4-F444-425E-8478-FDA531322F45@magma.ca>
	<1879720d0808110450h1bbfe9cep9b1d6a389706716b@mail.gmail.com>
X-Mailer: Apple Mail (2.926)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.2]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1118957727=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--===============1118957727==
Content-Type: multipart/alternative; boundary=Apple-Mail-3--1072260


--Apple-Mail-3--1072260
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

On Mon, 11-Aug-08, at 07:50 , Benny Prijono wrote:

> On Fri, Aug 8, 2008 at 9:08 PM, Philip Matthews <philip_matthews@magma.ca 
> > wrote:
>
> How about the following text? This is an attempt to give guidance  
> while leaving the final decision of what to do up to the implementor.
>
> 10.3.  Receiving a ChannelBind Response
>
>    When the client receives a ChannelBind success response, it updates
>    its data structures to record that the channel binding is now  
> active.
>
>    If the client receives a ChannelBind failure response that  
> indicates
>    that the channel information is out-of-sync between the client and
>    the server (e.g., an unexpected 400 "Bad Request" response), then  
> it
>    is RECOMMENDED that the client immediately delete the allocation  
> and
>    start afresh with a new allocation.
>
>
> I guess I'm okay with that. But we really want to handle out-of-sync  
> situation, can't we just add a new error code for this (e.g. 4xx  
> Channel In Use)?
>
> This way the situation is more explicit, and client can also (ab)use  
> it to check if a specified channel is currently in use (i.e. by  
> sending ChannelBind and see if it receives 4xx Channel In Use  
> response).

The problem with this approach to determining if a channel N is in use  
is, if it was not in use, then this approach will bind it to some  
address and that binding will take 10 minutes to expire. That is why I  
added an open issue to TURN-09 about adding a mechanism to determine  
if a channel was bound. But the sense of the ad-hoc meeting in Dublin  
was to avoid adding anything in this area and to just add some words  
about what to do if a ChannelBind fails.

>
>
> Cheers
>  Benny
>


--Apple-Mail-3--1072260
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>On Mon, =
11-Aug-08, at 07:50 , Benny Prijono wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
dir=3D"ltr">On Fri, Aug 8, 2008 at 9:08 PM, Philip Matthews <span =
dir=3D"ltr">&lt;<a =
href=3D"mailto:philip_matthews@magma.ca">philip_matthews@magma.ca</a>></sp=
an> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt =
0.8ex; padding-left: 1ex;"> <div style=3D""><div><br><div>How about the =
following text? This is an attempt to give guidance while leaving the =
final decision of what to do up to the =
implementor.</div><div><br></div><div><div>10.3. &nbsp;Receiving a =
ChannelBind Response</div> <div><br></div><div>&nbsp;&nbsp; When the =
client receives a ChannelBind success response, it =
updates</div><div>&nbsp;&nbsp; its data structures to record that the =
channel binding is now active.</div><div><br></div><div>&nbsp;&nbsp; If =
the client receives a ChannelBind failure response that indicates</div> =
<div>&nbsp;&nbsp; that the channel information is out-of-sync between =
the client and</div><div>&nbsp;&nbsp; the server (e.g., an unexpected =
400 "Bad Request" response), then it</div><div>&nbsp;&nbsp; is =
RECOMMENDED that the client immediately delete the allocation and</div> =
<div>&nbsp;&nbsp; start afresh with a new =
allocation.</div><div><br></div></div><font =
color=3D"#888888"><div></div></font></div></div></blockquote><div><br></di=
v></div>I guess I'm okay with that. But we really want to handle =
out-of-sync situation, can't we just add a new error code for this (e.g. =
4xx Channel In Use)?<br> <br>This way the situation is more explicit, =
and client can also (ab)use it to check if a specified channel is =
currently in use (i.e. by sending ChannelBind and see if it receives 4xx =
Channel In Use response).</div></blockquote><div><br></div><div>The =
problem with this approach to determining if a channel N is in use is, =
if it was not in use, then this approach will bind it to some address =
and that binding will take 10 minutes to expire. That is why I added an =
open issue to TURN-09 about adding a mechanism to determine if a channel =
was bound. But the sense of the ad-hoc meeting in Dublin was to avoid =
adding anything in this area and to just add some words about what to do =
if a ChannelBind fails.</div><br><blockquote type=3D"cite"><div =
dir=3D"ltr"><br><br>Cheers<br> =
&nbsp;Benny<br><br></div></blockquote></div><br></div></body></html>=

--Apple-Mail-3--1072260--

--===============1118957727==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

--===============1118957727==--


From behave-bounces@ietf.org  Fri Aug 15 13:17:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C35B03A6ADB;
	Fri, 15 Aug 2008 13:17:26 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2288B3A6ADB
	for <behave@core3.amsl.com>; Fri, 15 Aug 2008 13:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.261
X-Spam-Level: 
X-Spam-Status: No, score=-1.261 tagged_above=-999 required=5 tests=[AWL=1.338, 
	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 TPJzhR85ZM78 for <behave@core3.amsl.com>;
	Fri, 15 Aug 2008 13:17:25 -0700 (PDT)
Received: from mail-09.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 2B11F3A6898
	for <behave@ietf.org>; Fri, 15 Aug 2008 13:17:25 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.2])
	by mail-09.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KU5jg-0001oF-0n; Fri, 15 Aug 2008 16:17:24 -0400
Message-Id: <262460D0-C2AE-4729-80BB-E63344308DDD@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
In-Reply-To: <4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 15 Aug 2008 14:51:38 -0400
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>	<48949422.4080103@db.org>
	<4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
	<489CE00F.3050500@acm.org>
	<4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
X-Mailer: Apple Mail (2.926)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.2]) [24.139.16.154]
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Fri, 8-Aug-08, at 21:10 , Philip Matthews wrote:
>
> After thinking about this feature a bit, and taking Alfred's comment  =

> into account, it seems to me that there might be a platform where  =

> this feature cannot be implemented with an unprivileged user-space  =

> implementation. For example, a quick web search on how to do this  =

> for MacOS seemed to indicate that there might be a problem. Without  =

> getting into a discussion of which platforms can and cannot do it,  =

> it seems wise to me to treat this as a feature which an  =

> implementation might not be willing or able to support.
>
> Hence I have the following proposal for how to define this feature:
>
> 1) TURN would define a new attribute, call it SET-DF. The attribute  =

> would have a value length of 0. The attribute would be in the  =

> comprehension-required range.
>
> 2) A client MAY include the SET-DF option in an Allocate request.  =

> Including this option means that the client is requesting an  =

> allocation that supports this feature.
>
> 3) If the server cannot create an allocation that supports the  =

> feature, the Allocate request is rejected with a 420 Unknown  =

> Attributes and the UNKNOWN-ATTRIBUTES attribute would list this  =

> attribute. [Note that in this case, the SET-DF attribute may not  =

> really be unknown, but simply cannot be supported.]
>
> 4) If the server accepts the Allocate request, then the client MAY  =

> use the SET-DF attribute in a Send request or a Send indication. If  =

> the attribute is included, then the server sets the DF bit in the  =

> corresponding UDP datagram towards the peer. If the attribute is not  =

> included, the server does not set the DF bit.
>
> 5) Using the SET-DF attribute in a Send request or Send indication  =

> on an allocation that does not support it causes the Send request to  =

> be rejected and the Send indication to be silently ignored (=3D  =

> standard behavior for a unknown comprehension-required attribute).
>
> An alternative to this would be to drop points (2) and (3), and say  =

> that the server rejects a Send request if it cannot	 support the SET- =

> DF attribute. This is a bit simpler, but delays the point at which  =

> the client discovers that the attribute is not supported.
>
> Comments?


I have seen two requests for the simpler alternative described in the  =

last paragraph, and no requests for my more complex proposal. Since I  =

really don't care either way, I will go with the simpler proposal.



On Mon, 11-Aug-08, at 03:08 , R=E9mi Denis-Courmont wrote:
>
> What happens if SET-DF is *absent* and the OS does not support NOT  =

> setting the
> DF bit (from userland)? I recall BSDs, including OSX being in such  =

> situation.


The original request was for a way to do some sort of Path MTU  =

discovery when the server operated entirely in userland. Always  =

setting the DF bit doesn't interfere with this, it just means the the  =

Path MTU is smaller than it might otherwise be.

To be precise, if the SET-DF (or DONT-FRAGMENT, as Simon suggests)  =

attribute is not present, then I propose the text say that the server  =

SHOULD clear the DF bit, with a note that clearing the DF bit may not  =

be possible in some situations.

- Philip


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Aug 18 15:43:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6DC403A6834;
	Mon, 18 Aug 2008 15:43:09 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3A2B3A6834
	for <behave@core3.amsl.com>; Mon, 18 Aug 2008 15:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level: 
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.056, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 TRtNv+WR1Z6X for <behave@core3.amsl.com>;
	Mon, 18 Aug 2008 15:43:07 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 6DB1B3A67F5
	for <behave@ietf.org>; Mon, 18 Aug 2008 15:43:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,230,1217808000"; d="scan'208";a="141733571"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 18 Aug 2008 22:43:14 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m7IMhEAT007575
	for <behave@ietf.org>; Mon, 18 Aug 2008 15:43:14 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m7IMhE9j015012
	for <behave@ietf.org>; Mon, 18 Aug 2008 22:43:14 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
Date: Mon, 18 Aug 2008 15:43:13 -0700
Message-ID: <03f401c90183$ccaea170$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AckBg8xREQhNHCJWSzORAPa1QkoNHg==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=176; t=1219099394; x=1219963394;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20minutes=20posted |Sender:=20;
	bh=wnoe4aoVMThXoXy/Ntu3lKfcvguJ+LmkxUvouqS/0ak=;
	b=h6itzKmFyKQjS5lCv5AAxF7EtsiiYQFK7gH8OC1iuyrTImJYt/PehKdwAr
	GBcB8cW9QH+MR8aBnJNY9gX8HLAVZGhPHucHnaO6aZfPOMB8K6UEetXwZVPp
	x5Zq6bWayw;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [BEHAVE] minutes posted
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

BEHAVE minutes from Dublin are now at:

  http://www.ietf.org/proceedings/08jul/minutes/behave.txt

Please email me if you have changes or additions to the minutes.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug 19 07:11:25 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE5DA28C1A8;
	Tue, 19 Aug 2008 07:11:25 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9295128C166
	for <behave@core3.amsl.com>; Tue, 19 Aug 2008 07:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 t03LFk8fO3Sv for <behave@core3.amsl.com>;
	Tue, 19 Aug 2008 07:11:23 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id A52C728C161
	for <behave@ietf.org>; Tue, 19 Aug 2008 07:11:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,235,1217808000"; d="scan'208";a="67235967"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 19 Aug 2008 14:11:26 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m7JEBQwU030717; 
	Tue, 19 Aug 2008 07:11:26 -0700
Received: from [192.168.1.64] (sjc-vpn6-294.cisco.com [10.21.121.38])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m7JEBP0p012188;
	Tue, 19 Aug 2008 14:11:25 GMT
Message-Id: <76B1103E-4739-406D-9A6F-FC0DFB081CA9@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: Philip Matthews <philip_matthews@magma.ca>
In-Reply-To: <262460D0-C2AE-4729-80BB-E63344308DDD@magma.ca>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Tue, 19 Aug 2008 08:11:23 -0600
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>	<48949422.4080103@db.org>
	<4BE6EE36-ADCC-47FF-AEBC-01CF92138400@magma.ca>
	<489CE00F.3050500@acm.org>
	<4672FAA2-0593-4D84-B554-BE006C358DF2@magma.ca>
	<262460D0-C2AE-4729-80BB-E63344308DDD@magma.ca>
X-Mailer: Apple Mail (2.928.1)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3492; t=1219155086;
	x=1220019086; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20Proposed=20resolutions=20for
	=20TURN=20open=20issues |Sender:=20;
	bh=yNkS3peBuntGJbsajbMG6A/wpLvxSXFO8JAGtXXP1Dg=;
	b=xjv4pIa+HfLANp0NdbaN8eEGVRHAuMAsGD9qwVliv0j5AWpRNaLKl7YNeq
	8RUCaR4qHCqfh6eb77ld0OfS+NaDvgSZkz7k4mMddOK+5kYRuqvRAnE00vlW
	Sz+nFNxNNH;
Authentication-Results: sj-dkim-2; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Aug 15, 2008, at 12:51 , Philip Matthews wrote:

>
> On Fri, 8-Aug-08, at 21:10 , Philip Matthews wrote:
> >
> > After thinking about this feature a bit, and taking Alfred's comment
> > into account, it seems to me that there might be a platform where
> > this feature cannot be implemented with an unprivileged user-space
> > implementation. For example, a quick web search on how to do this
> > for MacOS seemed to indicate that there might be a problem. Without
> > getting into a discussion of which platforms can and cannot do it,
> > it seems wise to me to treat this as a feature which an
> > implementation might not be willing or able to support.
> >
> > Hence I have the following proposal for how to define this feature:
> >
> > 1) TURN would define a new attribute, call it SET-DF. The attribute
> > would have a value length of 0. The attribute would be in the
> > comprehension-required range.
> >
> > 2) A client MAY include the SET-DF option in an Allocate request.
> > Including this option means that the client is requesting an
> > allocation that supports this feature.
> >
> > 3) If the server cannot create an allocation that supports the
> > feature, the Allocate request is rejected with a 420 Unknown
> > Attributes and the UNKNOWN-ATTRIBUTES attribute would list this
> > attribute. [Note that in this case, the SET-DF attribute may not
> > really be unknown, but simply cannot be supported.]
> >
> > 4) If the server accepts the Allocate request, then the client MAY
> > use the SET-DF attribute in a Send request or a Send indication. If
> > the attribute is included, then the server sets the DF bit in the
> > corresponding UDP datagram towards the peer. If the attribute is not
> > included, the server does not set the DF bit.
> >
> > 5) Using the SET-DF attribute in a Send request or Send indication
> > on an allocation that does not support it causes the Send request to
> > be rejected and the Send indication to be silently ignored (=3D
> > standard behavior for a unknown comprehension-required attribute).
> >
> > An alternative to this would be to drop points (2) and (3), and say
> > that the server rejects a Send request if it cannot    support the  =

> SET-
> > DF attribute. This is a bit simpler, but delays the point at which
> > the client discovers that the attribute is not supported.
> >
> > Comments?
>
>
> I have seen two requests for the simpler alternative described in the
> last paragraph, and no requests for my more complex proposal. Since I
> really don't care either way, I will go with the simpler proposal.
>
>
>
> On Mon, 11-Aug-08, at 03:08 , R=E9mi Denis-Courmont wrote:
> >
> > What happens if SET-DF is *absent* and the OS does not support NOT
> > setting the
> > DF bit (from userland)? I recall BSDs, including OSX being in such
> > situation.
>
>
> The original request was for a way to do some sort of Path MTU
> discovery when the server operated entirely in userland. Always
> setting the DF bit doesn't interfere with this, it just means the the
> Path MTU is smaller than it might otherwise be.
>
> To be precise, if the SET-DF (or DONT-FRAGMENT, as Simon suggests)
> attribute is not present, then I propose the text say that the server
> SHOULD clear the DF bit, with a note that clearing the DF bit may not
> be possible in some situations.
>
> - Philip
>
>
>

Uh, what sitituations is it not possible to clear the DF bit?


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug 19 07:22:44 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 560DE3A68B8;
	Tue, 19 Aug 2008 07:22:44 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C66E3A6820
	for <behave@core3.amsl.com>; Tue, 19 Aug 2008 07:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 BGMP0rcppqx4 for <behave@core3.amsl.com>;
	Tue, 19 Aug 2008 07:22:42 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 518D33A67A3
	for <behave@ietf.org>; Tue, 19 Aug 2008 07:22:42 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m7JEKjRC013018; Tue, 19 Aug 2008 09:21:02 -0500
Received: from vaebh103.NOE.Nokia.com ([10.160.244.24]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 19 Aug 2008 17:18:46 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 19 Aug 2008 17:18:45 +0300
Received: from esdhcp040131.research.nokia.com ([172.21.40.131]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 19 Aug 2008 17:18:44 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: "ext Cullen Jennings" <fluffy@cisco.com>
Date: Tue, 19 Aug 2008 17:18:44 +0300
User-Agent: KMail/1.9.9
References: <03A7040C-D760-4237-91CE-982AEBC9807C@magma.ca>
	<262460D0-C2AE-4729-80BB-E63344308DDD@magma.ca>
	<76B1103E-4739-406D-9A6F-FC0DFB081CA9@cisco.com>
In-Reply-To: <76B1103E-4739-406D-9A6F-FC0DFB081CA9@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200808191718.44552.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 19 Aug 2008 14:18:44.0896 (UTC)
	FILETIME=[7D1E3200:01C90206]
X-Nokia-AV: Clean
Cc: BEHAVE WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] Proposed resolutions for TURN open issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Tuesday 19 August 2008 17:11:23 ext Cullen Jennings, you wrote:
> Uh, what sitituations is it not possible to clear the DF bit?

AFAIK, on a *BSD kernel (including MacOS X), all UDP datagrams have the DF =
bit =

_not_ set.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 20 06:06:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C18333A6A1D;
	Wed, 20 Aug 2008 06:06:19 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12CC03A682A;
	Wed, 20 Aug 2008 06:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.779
X-Spam-Level: 
X-Spam-Status: No, score=-0.779 tagged_above=-999 required=5
	tests=[AWL=-1.509, BAYES_05=-1.11, J_CHICKENPOX_13=0.6,
	SARE_LWSHORTT=1.24]
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 vyfR68zoChGU; Wed, 20 Aug 2008 06:06:15 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130])
	by core3.amsl.com (Postfix) with ESMTP id ADF3B3A686B;
	Wed, 20 Aug 2008 06:06:14 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1])
	by smtp.piuha.net (Postfix) with ESMTP id 33549198746;
	Wed, 20 Aug 2008 16:06:22 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130])
	by smtp.piuha.net (Postfix) with ESMTP id E91BA19867B;
	Wed, 20 Aug 2008 16:06:21 +0300 (EEST)
Message-ID: <48AC1715.2000808@piuha.net>
Date: Wed, 20 Aug 2008 16:07:33 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>, behave@ietf.org, 
	'IPv6 Operations' <v6ops@ops.ietf.org>, softwires@ietf.org
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [BEHAVE] next steps for ipv4-ipv6 co-existence and an interim
	meeting
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

We had many discussions about the IPv4 and IPv6 co-existence, NAT-PT
replacement, and new tunneling or translation solutions in Dublin. My
interpretation of the outcome is that some solutions are ready to move
forward (dual-stack lite to prevent running out of RFC 1918 addresses),
we improved our understanding of the translation designs (nat64 etc),
but that we were less far along in agreeing about the requirements for
that than we had hoped. In the INTAREA meeting you saw us go back to the
question of what scenarios we intend to address. We did not come to a
conclusion on that either, but private discussions afterwards have
convinced at least the INT ADs that we have a real business need for 2-3
different scenarios, requiring different solutions. The reality is that
existing NAT-PT is going to be used for some of these purposes unless
the IETF produces something better. I believe we can improve over the
existing design, and given that the mission of the IETF is to improve
the Internet, it is our duty to make this happen. To do this, we do not
need to find one perfect solution to all scenarios, enumerate all the
different situations that we'll encounter in the future, or even have a
solution that is completely free of problems. All we need to do is to
improve over what would happen otherwise.

With this in mind, I see the following short term next steps:
- Mark and I will produce a scenarios document that describes what
situations we must solve
- SOFTWIRE WG will be rechartered to add a work item on dual-stack
lite/snat (token: SOFTWIRE chairs)
- Progress the spec on dual-stack lite/snat (token: authors)
- For the rest, we need a written analysis of the overall design space
(token: Dan Wing and Alain Durand have agreed to do this)
- Progress the specs for the different translation-based proposals,
based on feedback in Dublin (token: authors)
- More discussion is needed on implications of "carrier-grade NATs" in
the pure IPv4 space

Did I miss anything?

We are also planning to run an interim meeting. The goal would be to
provide enough time to talk about this topic, and make significant
progress before IETF-73. This would be a meeting that affects work
happening in a number of WGs (SOFTWIRE, V6OPS, BEHAVE, INTAREA) and
different solutions for different scenarios. The agenda for the meeting
will be posted later, but it contains slots to talk about the scenarios,
design space, and each different solution approach.

The dates are October 1-2 and the likely location is Montreal, Canada.
We are currently working to confirm availability of meeting space and
other arrangements. So please consider this information tentative at the
moment; if we get surprises this may still change. However, for venue
selection we would like to learn how many people would join such a
meeting. Please fill in a poll here:

http://www.doodle.ch/participation.html?pollId=xw744qvw725cbsfm

Follow-ups regarding the general plan and the interim to intarea only,
please.

Jari Arkko
(on behalf of the ADs and WG chairs)


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 20 07:29:39 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1027B28B56A;
	Wed, 20 Aug 2008 07:29:39 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 39FDD28B56A;
	Wed, 20 Aug 2008 07:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level: 
X-Spam-Status: No, score=-0.4 tagged_above=-999 required=5 tests=[AWL=0.309,
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3,
	SARE_LWSHORTT=1.24]
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 R8v8gqCYYjKs; Wed, 20 Aug 2008 07:29:37 -0700 (PDT)
Received: from smtp7-g19.free.fr (smtp7-g19.free.fr [212.27.42.64])
	by core3.amsl.com (Postfix) with ESMTP id 580353A6C40;
	Wed, 20 Aug 2008 07:29:37 -0700 (PDT)
Received: from smtp7-g19.free.fr (localhost [127.0.0.1])
	by smtp7-g19.free.fr (Postfix) with ESMTP id 9B297B0002;
	Wed, 20 Aug 2008 16:29:21 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp7-g19.free.fr (Postfix) with ESMTP id 2096CB0193;
	Wed, 20 Aug 2008 16:29:20 +0200 (CEST)
Message-ID: <48AC2A06.4090407@free.fr>
Date: Wed, 20 Aug 2008 16:28:22 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <48AC1715.2000808@piuha.net>
In-Reply-To: <48AC1715.2000808@piuha.net>
Cc: 'IPv6 Operations' <v6ops@ops.ietf.org>, behave@ietf.org, softwires@ietf.org,
	Internet Area <int-area@ietf.org>
Subject: Re: [BEHAVE] next steps for ipv4-ipv6 co-existence and an interim
 meeting
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Jari Arkko  le (m/j/a) 8/20/08 3:07 PM:

> With this in mind, I see the following short term next steps:
> - Mark and I will produce a scenarios document that describes what
> situations we must solve
> - SOFTWIRE WG will be rechartered to add a work item on dual-stack
> lite/snat (token: SOFTWIRE chairs)
> - Progress the spec on dual-stack lite/snat (token: authors)
> - For the rest, we need a written analysis of the overall design space
> (token: Dan Wing and Alain Durand have agreed to do this)
> - Progress the specs for the different translation-based proposals,
> based on feedback in Dublin (token: authors)
> - More discussion is needed on implications of "carrier-grade NATs" in
> the pure IPv4 space
> =

> Did I miss anything?

Just a detail, but IMHO worth validating.

Can it be assumed that the last but one item "Progress the specs for
the different _translation-based_ proposals..." is in practice open to
a proposal that avoids translation?

The reason for the question is the proposal that is worked on, following =

the APBP presentation in Dublin, with interest expressed in particular =

by Teemu Savolainen and Gabor Bajko of Nokia.

With it, translation is completely avoided in scenario 1.d of Mark's =

presentation (DS host accessing the IPv4-only world through an IPv6-only =

cloud).
This transparency of global IPv4 across tunnels is naturally seen as a =

positive point of the design.

Regards.

R=E9mi Despr=E9s



_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Aug 20 08:26:34 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 965763A68CC;
	Wed, 20 Aug 2008 08:26:34 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 89AE83A6C37;
	Wed, 20 Aug 2008 07:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.352
X-Spam-Level: 
X-Spam-Status: No, score=-0.352 tagged_above=-999 required=5
	tests=[AWL=-4.110, BAYES_00=-2.599, FS_BROKEN_MEETING=10.357,
	RCVD_IN_DNSWL_MED=-4]
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 YtC11K8eEUW6; Wed, 20 Aug 2008 07:47:03 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69])
	by core3.amsl.com (Postfix) with ESMTP id 711E83A6BC8;
	Wed, 20 Aug 2008 07:46:37 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id m7KEjoaF015815
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 20 Aug 2008 07:45:55 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	m7KEjnSi017367; Wed, 20 Aug 2008 09:45:49 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	m7KEjgu6017060; Wed, 20 Aug 2008 09:45:49 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 20 Aug 2008 07:45:47 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 20 Aug 2008 07:45:45 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A104DEE9E6@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <48AC1715.2000808@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Int-area] next steps for ipv4-ipv6 co-existence and an
	interimmeeting
Thread-Index: AckCxZAYpCoRmF0JT2SzLVVN5pcR0gADZEVw
References: <48AC1715.2000808@piuha.net>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Jari Arkko" <jari.arkko@piuha.net>, "Internet Area" <int-area@ietf.org>, 
	<behave@ietf.org>, "IPv6 Operations" <v6ops@ops.ietf.org>,
	<softwires@ietf.org>
X-OriginalArrivalTime: 20 Aug 2008 14:45:47.0694 (UTC)
	FILETIME=[6ECB44E0:01C902D3]
X-Mailman-Approved-At: Wed, 20 Aug 2008 08:26:33 -0700
Subject: Re: [BEHAVE] [Int-area] next steps for ipv4-ipv6 co-existence and
	an interimmeeting
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Jari,

>Did I miss anything?

I was not able to attend the meeting; were considerations
for ipv4-ipv6 coexistence in enterprise networks discussed?

Fred
fred.l.templin@boeing.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug 22 11:11:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 534713A6A29;
	Fri, 22 Aug 2008 11:11:03 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A05AA3A6A29
	for <behave@core3.amsl.com>; Fri, 22 Aug 2008 11:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.232
X-Spam-Level: 
X-Spam-Status: No, score=-1.232 tagged_above=-999 required=5 tests=[AWL=0.744, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 J3veZ0p4Q76T for <behave@core3.amsl.com>;
	Fri, 22 Aug 2008 11:11:01 -0700 (PDT)
Received: from s200aog14.obsmtp.com (s200aog14.obsmtp.com [207.126.144.128])
	by core3.amsl.com (Postfix) with SMTP id E5D773A67CF
	for <behave@ietf.org>; Fri, 22 Aug 2008 11:11:00 -0700 (PDT)
Received: from source ([209.85.198.224]) by eu1sys200aob014.postini.com
	([207.126.147.11]) with SMTP; Fri, 22 Aug 2008 18:10:33 UTC
Received: by rv-out-0506.google.com with SMTP id k40so684401rvb.19
	for <behave@ietf.org>; Fri, 22 Aug 2008 11:10:32 -0700 (PDT)
Received: by 10.140.127.13 with SMTP id z13mr673484rvc.194.1219428632540;
	Fri, 22 Aug 2008 11:10:32 -0700 (PDT)
Received: by 10.141.186.2 with HTTP; Fri, 22 Aug 2008 11:10:32 -0700 (PDT)
Message-ID: <1879720d0808221110l1dbf69eeg87f45192f0428aa4@mail.gmail.com>
Date: Fri, 22 Aug 2008 19:10:32 +0100
From: "Benny Prijono" <bennylp@pjsip.org>
To: "BEHAVE WG" <behave@ietf.org>
MIME-Version: 1.0
X-Google-Sender-Auth: e95ea3026a4a29f3
Subject: [BEHAVE] Some TURN-09 comments
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1679919939=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

--===============1679919939==
Content-Type: multipart/alternative; 
	boundary="----=_Part_36614_22986514.1219428632535"

------=_Part_36614_22986514.1219428632535
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

Some minor comments.

- SOFTWARE-TYPE attribute
  The attribute name is inconsistent with rfc3489bis-18, which calls it with
just SOFTWARE. On the other hand,
http://www.employees.org/behave/stun-attributes.html also calls it
SOFTWARE-TYPE, so I'm not sure which one should be fixed.

- ICMP attribute code number
  The code number is 0x0030, which is not wrong, but IMO it'll be better to
change it to 0x002a since this slot is free. The reason is because
implementors (or at least me) like to implement the attribute descriptors as
an array, and with 0x0030 there is an wasted gap from 0x002a to 0x002f. Not
a big deal, but there's no reason to waste space either, and IMO it's not
too late to change it.

- I think the Note in Section 6.2 (page 20/21) about server remembering last
error response is not necessary. The rfc3489bis-18 already says that server
SHOULD retransmit last error response. And in fact the text in that Note
that says:

 "Server implementors MAY elect to prevent this second case by
  remembering recent failure responses and returning the saved
  failure response when receiving a retransmitted Allocate request."

 contradicts the SHOULD requirement in rfc3489bis-18, thus should be deleted
IMO.

Cheers
 Benny

------=_Part_36614_22986514.1219428632535
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Hi,<br><br>Some minor comments.<br><br>- SOFTWARE-TYPE attribute<br>&nbsp; The attribute name is inconsistent with rfc3489bis-18, which calls it with just SOFTWARE. On the other hand, <a href="http://www.employees.org/behave/stun-attributes.html">http://www.employees.org/behave/stun-attributes.html</a> also calls it SOFTWARE-TYPE, so I&#39;m not sure which one should be fixed.<br>
<br>- ICMP attribute code number<br>&nbsp; The code number is 0x0030, which is not wrong, but IMO it&#39;ll be better to change it to 0x002a since this slot is free. The reason is because implementors (or at least me) like to implement the attribute descriptors as an array, and with 0x0030 there is an wasted gap from 0x002a to 0x002f. Not a big deal, but there&#39;s no reason to waste space either, and IMO it&#39;s not too late to change it.<br>
<br>- I think the Note in Section 6.2 (page 20/21) about server remembering last error response is not necessary. The rfc3489bis-18 already says that server SHOULD retransmit last error response. And in fact the text in that Note that says:<br>
<br>&nbsp;&quot;Server implementors MAY elect to prevent this second case by<br>&nbsp; remembering recent failure responses and returning the saved<br>&nbsp; failure response when receiving a retransmitted Allocate request.&quot;<br><br>
&nbsp;contradicts the SHOULD requirement in rfc3489bis-18, thus should be deleted IMO.<br><br>Cheers<br>&nbsp;Benny<br><br><br></div>

------=_Part_36614_22986514.1219428632535--

--===============1679919939==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

--===============1679919939==--


From behave-bounces@ietf.org  Fri Aug 22 17:14:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9066028C137;
	Fri, 22 Aug 2008 17:14:51 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68D9F3A6A49;
	Fri, 22 Aug 2008 17:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.091
X-Spam-Level: 
X-Spam-Status: No, score=-5.091 tagged_above=-999 required=5
	tests=[AWL=-0.032, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24]
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 Qsmb52zghL4C; Fri, 22 Aug 2008 17:14:49 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 8B6C53A67EB;
	Fri, 22 Aug 2008 17:14:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,255,1217808000"; d="scan'208";a="77600240"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-2.cisco.com with ESMTP; 23 Aug 2008 00:14:47 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m7N0El68009932; 
	Fri, 22 Aug 2008 17:14:47 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m7N0Eke0021058;
	Sat, 23 Aug 2008 00:14:46 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>,
	"'Jari Arkko'" <jari.arkko@piuha.net>
References: <48AC1715.2000808@piuha.net> <48AC2A06.4090407@free.fr>
Date: Fri, 22 Aug 2008 17:14:46 -0700
Message-ID: <19a601c904b5$40531c30$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AckC0TLFz9pCYxHhToGNAmF3r4M/uwB461jw
In-Reply-To: <48AC2A06.4090407@free.fr>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1860; t=1219450487;
	x=1220314487; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20next=20steps=20for=20ipv4-ip
	v6=20co-existence=20and=20an=20interim=20meeting |Sender:=20;
	bh=xtvz3HL6d8xE94a4UdsJ/IHYidulgzZP1Fqil5l4CaY=;
	b=TWPvi5lMSOhk+hlZikxM3ZJwfNaoGmQuLD7jQ+lyjK+hl7o9fRRnfcpmzJ
	Hn9ciKbHPEay0lFx6YQa9laqQ4mjBeu0JrFKnIT4dYMwQHOlDiK9BbPNjhMX
	qYJYt8bXMh;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: 'IPv6 Operations' <v6ops@ops.ietf.org>, softwires@ietf.org,
	'Internet Area' <int-area@ietf.org>, behave@ietf.org
Subject: Re: [BEHAVE] next steps for ipv4-ipv6 co-existence and an interim
	meeting
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> > With this in mind, I see the following short term next steps:
> > - Mark and I will produce a scenarios document that describes what
> > situations we must solve
> > - SOFTWIRE WG will be rechartered to add a work item on dual-stack
> > lite/snat (token: SOFTWIRE chairs)
> > - Progress the spec on dual-stack lite/snat (token: authors)
> > - For the rest, we need a written analysis of the overall 
> > design space
> > (token: Dan Wing and Alain Durand have agreed to do this)
> > - Progress the specs for the different translation-based proposals,
> > based on feedback in Dublin (token: authors)
> > - More discussion is needed on implications of 
> > "carrier-grade NATs" in the pure IPv4 space
> > 
> > Did I miss anything?
> 
> Just a detail, but IMHO worth validating.
> 
> Can it be assumed that the last but one item "Progress the specs for
> the different _translation-based_ proposals..." is in practice open to
> a proposal that avoids translation?
> 
> The reason for the question is the proposal that is worked 
> on, following the APBP presentation in Dublin, with interest 
> expressed in particular by Teemu Savolainen and Gabor Bajko of 
> Nokia.
> 
> With it, translation is completely avoided in scenario 1.d of Mark's 
> presentation (DS host accessing the IPv4-only world through 
> an IPv6-only cloud).
> This transparency of global IPv4 across tunnels is naturally 
> seen as a positive point of the design.

I would consider that 'host-based translation', and hence 
in scope of what Jari mentioned.  With host-based translation,
the host is doing the translation instead of a device in the 
network.  Depending on how it is implemented in the host, it 
could be the host application or the host's stack that 'borrows'
the IPv4 transport address.

I look forward to reading the I-D.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug 22 17:19:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8CB163A6ADE;
	Fri, 22 Aug 2008 17:19:24 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E29F3A6ADA;
	Fri, 22 Aug 2008 17:19:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.676
X-Spam-Level: 
X-Spam-Status: No, score=-0.676 tagged_above=-999 required=5
	tests=[AWL=-4.434, BAYES_00=-2.599, FS_BROKEN_MEETING=10.357,
	RCVD_IN_DNSWL_MED=-4]
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 JzG57JWhyph8; Fri, 22 Aug 2008 17:19:22 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 4EC273A67EB;
	Fri, 22 Aug 2008 17:19:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,255,1217808000"; d="scan'208";a="77601002"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 23 Aug 2008 00:19:32 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m7N0JWqR002166; 
	Fri, 22 Aug 2008 17:19:32 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m7N0JWDY021936;
	Sat, 23 Aug 2008 00:19:32 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>,
	"'Jari Arkko'" <jari.arkko@piuha.net>,
	"'Internet Area'" <int-area@ietf.org>, <behave@ietf.org>,
	"'IPv6 Operations'" <v6ops@ops.ietf.org>, <softwires@ietf.org>
References: <48AC1715.2000808@piuha.net>
	<39C363776A4E8C4A94691D2BD9D1C9A104DEE9E6@XCH-NW-7V2.nw.nos.boeing.com>
Date: Fri, 22 Aug 2008 17:19:32 -0700
Message-ID: <19a701c904b5$ea757e10$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AckCxZAYpCoRmF0JT2SzLVVN5pcR0gADZEVwAHiJGCA=
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A104DEE9E6@XCH-NW-7V2.nw.nos.boeing.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=549; t=1219450772; x=1220314772;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Softwires]=20[Int-area]=20next=20steps
	=20for=20ipv4-ipv6=20co-existenceand=20an=20interimmeeting
	|Sender:=20; bh=NeZjUuIem3812ye+NKAa/7wexhLbCl6NAHljVCRp/fI=;
	b=rMM6q2I+hdhQl5n+XKbybkKxOBp+PjcpUe0Lx756Alx19EEKjJdvoPee9F
	psIhXHMxGNMnN6GI+ZctJmi37NKflEYzrV0uCU8LnaKDbwedjA4+lhF9f1pA
	DqKTm1FX7P;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [BEHAVE] [Softwires] [Int-area] next steps for ipv4-ipv6
	co-existenceand an interimmeeting
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> >Did I miss anything?
> 
> I was not able to attend the meeting; were considerations
> for ipv4-ipv6 coexistence in enterprise networks discussed?

I believe most everyone is thinking of the Internet, rather
than enterprise networks.

If there are unique enterprise requirements it would be 
valuable to incorporate them into a requirements document 
(either in draft-ietf-v6ops-nat64-pb-statement-req or in the 
document that Jari's email said that Jari and Mark Townsley 
are writing -- I'm not sure which one would be best).

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug 26 03:40:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C915F28C103;
	Tue, 26 Aug 2008 03:40:02 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE24C3A6AD6;
	Tue, 26 Aug 2008 03:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.83
X-Spam-Level: 
X-Spam-Status: No, score=-2.83 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745,
	RCVD_IN_DNSWL_MED=-4]
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 MulqII1bLZp2; Tue, 26 Aug 2008 03:40:01 -0700 (PDT)
Received: from smtp.uibk.ac.at (lmr1.uibk.ac.at [138.232.1.142])
	by core3.amsl.com (Postfix) with ESMTP id BF9853A6804;
	Tue, 26 Aug 2008 03:40:00 -0700 (PDT)
Received: from [192.168.1.4] (host94-41-dynamic.4-87-r.retail.telecomitalia.it
	[87.4.41.94] florian.niederbacher@student.uibk.ac.at)
	(authenticated bits=0)
	by smtp.uibk.ac.at (8.13.8/8.13.8/F1) with ESMTP id m7QAdY5b026484
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 26 Aug 2008 12:39:35 +0200
Message-ID: <48B3DD62.9090303@student.uibk.ac.at>
Date: Tue, 26 Aug 2008 12:39:30 +0200
From: Florian Niederbacher <florian.niederbacher@student.uibk.ac.at>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: behave@ietf.org, tsvwg@ietf.org
X-Scanned-By: MIMEDefang 2.61 at uibk.ac.at on 138.232.1.140
Subject: [BEHAVE] SCTP NAT_attack
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,
I have read the NAT-draft[draft-stewart-behave-sctpnat] 
<http://tools.ietf.org/id/draft-stewart-behave-sctpnat-04.txt> from 
behavewg. I made a lot of practical tests with the NAT considerations, 
so that SCTP works now fine with them. On the other side this draft 
explains also how easily a "SCTP- NAT attack" can be done. If an 
attacker is able to read the IP traffic it can modify the IP address 
(like NAT it does). The receiver sends to the wrong IP an ABORT back. If 
this packet is then redirected to the original IP, a connection loss is 
the result. In this case an attacker has a possibility to shutdown SCTP 
connections. In RFC4960 (SCTP) and RFC 5062 (Security attacks SCTP) I 
couldn't find any information which matches this case.
My proposal would be to insert this kind of attack in RFC 5062.
Maybe I am missing something, then correct me please. What's your 
opinion about this scenario?

Best regards
Florian Niederbacher
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Aug 26 23:30:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F2CD3A69BC;
	Tue, 26 Aug 2008 23:30:52 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 989F83A695F;
	Tue, 26 Aug 2008 23:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.527
X-Spam-Level: ***
X-Spam-Status: No, score=3.527 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, HOST_EQ_DIP_TDIAL=2.144,
	HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=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 0i49my3zfzAl; Tue, 26 Aug 2008 23:30:49 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de
	[IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa])
	by core3.amsl.com (Postfix) with ESMTP id 506593A69BC;
	Tue, 26 Aug 2008 23:30:49 -0700 (PDT)
Received: from [192.168.1.15] (p508FFF08.dip.t-dialin.net [80.143.255.8])
	by mail-n.franken.de (Postfix) with ESMTP id DADC31C0C0BC0;
	Wed, 27 Aug 2008 08:30:44 +0200 (CEST)
Message-Id: <5181657B-1B77-45F1-B3B0-B5836486FB3A@lurchi.franken.de>
From: =?ISO-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
To: Florian Niederbacher <florian.niederbacher@student.uibk.ac.at>
In-Reply-To: <48B3DD62.9090303@student.uibk.ac.at>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Wed, 27 Aug 2008 08:30:43 +0200
References: <48B3DD62.9090303@student.uibk.ac.at>
X-Mailer: Apple Mail (2.926)
Cc: behave@ietf.org, tsvwg@ietf.org
Subject: Re: [BEHAVE] [Tsvwg] SCTP NAT_attack
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi Florian,

SCTP (except for extensive use of SCTP-AUTH) does not protect against  
on-path
attackers. They know the verification tags and when they can forge  
source
addresses can send all SCTP packets on behalf of one end-points. They  
can
not only terminate the association (send an ABORT) but also insert user
data and so on.

That is known and pretty common to other transport protocols like TCP,  
UDP
or DCCP.

Protection against on-path attackers is much harder than protection  
against
off-path attackers. If you want to protect your traffic also against  
on-path
attackers you can use SCTP-AUTH to authenticate all allowed chunks and  
use
for example DTLS to establish a shared secret. Then an on-path  
attacker is
not able anymore to insert DATA or terminate the association. However,
he can still just dump all packets and perform a DOS attacker. You can
only use multihoming to protect against that attack as long as the
on-path attacker is not an on-path attacker on all paths...

An RFC can not be changed. One could write another ID to obsolete a  
given
one. But the problem you describe is known since the pre RFC 2960 time
and not SCTP specific, so I would not spent the effort to write up a
new ID.

The usage of SCTP-AUTH to protect against on-path attackers is covered
in RFC 4895.

Best regards
Michael

On Aug 26, 2008, at 12:39 PM, Florian Niederbacher wrote:

> Hi,
> I have read the NAT-draft[draft-stewart-behave-sctpnat] <http://tools.ietf.org/id/draft-stewart-behave-sctpnat-04.txt 
> > from behavewg. I made a lot of practical tests with the NAT  
> considerations, so that SCTP works now fine with them. On the other  
> side this draft explains also how easily a "SCTP- NAT attack" can be  
> done. If an attacker is able to read the IP traffic it can modify  
> the IP address (like NAT it does). The receiver sends to the wrong  
> IP an ABORT back. If this packet is then redirected to the original  
> IP, a connection loss is the result. In this case an attacker has a  
> possibility to shutdown SCTP connections. In RFC4960 (SCTP) and RFC  
> 5062 (Security attacks SCTP) I couldn't find any information which  
> matches this case.
> My proposal would be to insert this kind of attack in RFC 5062.
> Maybe I am missing something, then correct me please. What's your  
> opinion about this scenario?
>
> Best regards
> Florian Niederbacher
>

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Aug 28 16:46:31 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A888828C125;
	Thu, 28 Aug 2008 16:46:31 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C8193A6AA4
	for <behave@core3.amsl.com>; Thu, 28 Aug 2008 16:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level: 
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5
	tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
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 WfP6kJCrPDjr for <behave@core3.amsl.com>;
	Thu, 28 Aug 2008 16:46:27 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 190E63A6A2D
	for <behave@ietf.org>; Thu, 28 Aug 2008 16:46:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,289,1217808000"; d="scan'208";a="98027101"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 28 Aug 2008 23:46:05 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m7SNk5cQ000836; 
	Thu, 28 Aug 2008 16:46:05 -0700
Received: from dhcp-128-107-102-125.cisco.com (dhcp-128-107-102-125.cisco.com
	[128.107.102.125])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m7SNk5QL027899;
	Thu, 28 Aug 2008 23:46:05 GMT
Message-Id: <71257564-FC90-4FAD-8567-30AA7E8E5A06@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: Philip Matthews <philip_matthews@magma.ca>
In-Reply-To: <2295C2E7-1EA0-49E2-803C-2B705D5B1474@magma.ca>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Thu, 28 Aug 2008 16:46:15 -0700
References: <2295C2E7-1EA0-49E2-803C-2B705D5B1474@magma.ca>
X-Mailer: Apple Mail (2.928.1)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1297; t=1219967165;
	x=1220831165; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20How=20to=20handle=20an=20uns
	upported=20class=20of=20a=20known=20STUN=20method? |Sender:=20;
	bh=O4zWWGE4AcwF2+9GNarTGruGYsuoG6C/GO7m80ukCOk=;
	b=mlekqx0K6nqjreBl280U/qHuO7ywWFb06ThmOhlcZwFpzxVEws/IoYQi9r
	UkztcMzQtVoF8f1FxF9TZ3XPgyYGF3v+HzLHtomLq41LL8RGR/23BPYsgrG7
	wPUD/En0OE;
Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] How to handle an unsupported class of a known STUN
	method?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


I'm don't see  what the issue is here. It seems like any specification  
that defined a new method would have to say what happened for all  
classes of that method. Any use of a class that was not specified for  
a method would be invalid to send.

On Aug 13, 2008, at 5:39 , Philip Matthews wrote:

> In section 7.3, draft-iet-behave-rfc3489bis-18 states that when a  
> received STUN message with an unknown method is received, the  
> message is silently discarded. However, it does not define how to  
> handle a receive message with a known method when the class is  
> unsupported; for example, an Allocate indication or a Data request,  
> to give two examples from TURN.
>
> I propose that this be clarified to say that the message is silently  
> ignored in this case.
>
> An alternative would be to silently ignore an unsupported  
> indication, but to return 400 Bad Request for an unsupported  
> request. However, this would mean that clients would have to be able  
> to return error responses, and Rohan has previously objected to  
> clients having to implement any sort of server-side processing.
>
> - Philip
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug 29 14:55:14 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C36203A6AFB;
	Fri, 29 Aug 2008 14:55:14 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4163C3A6AFB
	for <behave@core3.amsl.com>; Fri, 29 Aug 2008 14:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
	tests=[BAYES_50=0.001]
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 G31nokJ6m1bK for <behave@core3.amsl.com>;
	Fri, 29 Aug 2008 14:55:13 -0700 (PDT)
Received: from mail-08.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id B69053A6A3C
	for <behave@ietf.org>; Fri, 29 Aug 2008 14:55:12 -0700 (PDT)
Received: from dialin-207-112-29-246.tor.primus.ca ([207.112.29.246])
	by mail-08.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1KZBw3-0005hy-0L
	for behave@ietf.org; Fri, 29 Aug 2008 17:55:15 -0400
Message-Id: <A792718A-6C1C-4DD9-8D1F-6D3A19D68DD9@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 29 Aug 2008 17:55:21 -0400
X-Mailer: Apple Mail (2.926)
X-Authenticated: philip_matthews@magma.ca -
	dialin-207-112-29-246.tor.primus.ca [207.112.29.246]
Subject: [BEHAVE] SOFTWARE attribute in TURN
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Version -09 of the TURN spec says that the client and the server  
SHOULD include the SOFTWARE attribute (which TURN-09 called SOFTWARE- 
TYPE) in all requests and responses, but not in Send and Data  
indications.

However, on second thought, it seems a waste of bandwidth to include  
this attribute in all requests and responses. In particular, including  
it in Send requests seems unfortunate, since it reduces the maximum  
allowed size of the DATA attribute.

So unless I hear an objection, TURN-10 will say:

     The client SHOULD include the SOFTWARE attribute in all Allocate  
and Refresh requests
     and MAY include it in any other requests or indications. The  
server SHOULD include the
     SOFTWARE attribute in all Allocate and Refresh responses (either  
success or failure)
     and MAY include it in other responses or indications.


- Philip


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug 29 17:50:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 056C83A6B15;
	Fri, 29 Aug 2008 17:50:26 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D0F53A6B0A;
	Fri, 29 Aug 2008 17:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.649
X-Spam-Level: 
X-Spam-Status: No, score=-5.649 tagged_above=-999 required=5 tests=[AWL=0.950, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Uc5UoY6i5Kb0; Fri, 29 Aug 2008 17:50:22 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 1EB283A6B03;
	Fri, 29 Aug 2008 17:50:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,295,1217808000"; d="scan'208";a="71115521"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 30 Aug 2008 00:50:26 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m7U0oQgm030291; 
	Fri, 29 Aug 2008 17:50:26 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m7U0oQ6Q018681;
	Sat, 30 Aug 2008 00:50:26 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
References: <214901c8f8f5$7d5ea610$d35d150a@cisco.com>
Date: Fri, 29 Aug 2008 17:50:26 -0700
Message-ID: <0ebc01c90a3a$643a40d0$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj49Xzun/wVC6D6QQCAcBe4RCQB+ARRK8JQ
In-Reply-To: <214901c8f8f5$7d5ea610$d35d150a@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=874; t=1220057426; x=1220921426;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20WGLC=3A=20draft-ietf-behave-
	dccp-01 |Sender:=20;
	bh=NLxQeAQeXVjTj9P7+iCI4N0lsPSOaSLwJnyQxexdy3g=;
	b=CrH/qQb2ivZ+Cbeb6lGIXq0wlWyImCoHpzMlgYFcVb9bDBNSotHqgUkX2M
	BAnCLmBohylp/UrO/2/Tbc5rmVhOp+1dmoobK4Cs2PiCvwjEc5FsRT6/B5EV
	6mW0kSJ6SCyQgDNAKURfkKPNZXN465Psr2RPzsMD9BQhI2HTEnjoA=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: dccp@ietf.org, rem@videolan.org
Subject: Re: [BEHAVE] WGLC: draft-ietf-behave-dccp-01
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

BEHAVE's WGLC on draft-ietf-behave-dccp-01 has concluded.  Remi, please
integrate the comments received, publish -02, and I will request publication.

-d


> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> Sent: Thursday, August 07, 2008 6:24 PM
> To: Behave WG
> Cc: dccp@ietf.org; rem@videolan.org
> Subject: [BEHAVE] WGLC: draft-ietf-behave-dccp-01
> 
> Behave is commencing a 2-week WGLC for "Network Address 
> Translation (NAT)
> Behavioral Requirements for DCCP",
> <http://tools.ietf.org/html/draft-ietf-behave-dccp-01>.  The 
> WGLC will end on
> August 21.
> 
> Please send comments to the author and to Behave.
> 
> -d
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Aug 29 17:51:39 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 762C73A6B12;
	Fri, 29 Aug 2008 17:51:39 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5D3EE3A6B0E
	for <behave@core3.amsl.com>; Fri, 29 Aug 2008 17:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.887
X-Spam-Level: 
X-Spam-Status: No, score=-5.887 tagged_above=-999 required=5 tests=[AWL=0.712, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 zTNgaa9Dbmfm for <behave@core3.amsl.com>;
	Fri, 29 Aug 2008 17:51:37 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id CC7313A6B12
	for <behave@ietf.org>; Fri, 29 Aug 2008 17:51:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,295,1217808000"; d="scan'208";a="149436648"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 30 Aug 2008 00:51:39 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m7U0pcDi004343; 
	Fri, 29 Aug 2008 17:51:38 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m7U0pc8L018905;
	Sat, 30 Aug 2008 00:51:38 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
References: <214a01c8f8f5$c8d16060$d35d150a@cisco.com>
Date: Fri, 29 Aug 2008 17:51:38 -0700
Message-ID: <0ebd01c90a3a$8f8b1ed0$c2f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0EBE_01C909FF.E32C46D0"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acj49chXEUhnIsNDRWmJ5MkbBUEVngRRJ6ug
In-Reply-To: <214a01c8f8f5$c8d16060$d35d150a@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10098; t=1220057498;
	x=1220921498; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=202nd=20WGLC=20draft-ietf-beha
	ve-nat-behavior-discovery-04 |Sender:=20;
	bh=yXeCXvwqWKRBwXx+8DVV9kla9/ydYh50vhlfFdXMO3o=;
	b=YTld1W0nfjDceY3OE3IorDkUNF26twnnLYtIX1oybLNhfhB0oipYHiBe17
	erN+L8CDfJnbyxrfzvuUdtAbrhdE0Wb9gVmkbeu1MhGff/EwCNYjnnqv4rNF
	ZrVdaxbQ+V;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [BEHAVE] 2nd WGLC draft-ietf-behave-nat-behavior-discovery-04
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0EBE_01C909FF.E32C46D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The WGLC on draft-ietf-behave-nat-behavior-discovery-04 has concluded, with no
comments received.  I have requested publication of this document.  PROTO
writeup is attached.

-d


> -----Original Message-----
> From: behave-bounces@ietf.org 
> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> Sent: Thursday, August 07, 2008 6:26 PM
> To: Behave WG
> Subject: [BEHAVE] 2nd WGLC draft-ietf-behave-nat-behavior-discovery-04
> 
> I'd like to do a quick one week 2nd WGLC on "NAT Behavior 
> Discovery Using
> STUN",
> <http://tools.ietf.org/html/draft-ietf-behave-nat-behavior-dis
> covery-04>.
> This will end on August 14th.  
> 
> Please send comments to the authors (CC'd) and the list.
> 
> -d
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

------=_NextPart_000_0EBE_01C909FF.E32C46D0
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment

From: "Dan Wing" <dwing@cisco.com>
To: <iesg-secretary@ietf.org>,
	"'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Cc: "'Derek MacDonald'" <derek@counterpath.com>,
	"'Bruce Lowekamp'" <lowekamp@sipeerior.com>
Subject: pub request: draft-ietf-behave-nat-behavior-discovery-04.txt
Date: Fri, 29 Aug 2008 17:47:05 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AckKOexdaMITD1aGQYGst22LiMojRA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198

BEHAVE has finished its WGLC of
draft-ietf-behave-nat-behavior-discovery-04.txt, and request s this document
be published.

Thanks,
-d

-----

Document shepherd write-up for draft-ietf-behave-nat-behavior-discovery-04
date: 29-Aug-2008

   (1.a)  Who is the Document Shepherd for this document? 

Dan Wing, dwing@cisco.com

          Has the
          Document Shepherd personally reviewed this version of the
          document and, in particular, does he or she believe this
          version is ready for forwarding to the IESG for publication?

Yes.


   (1.b)  Has the document had adequate review both from key WG members
          and from key non-WG members?  Does the Document Shepherd have
          any concerns about the depth or breadth of the reviews that
          have been performed?

No concerns.


   (1.c)  Does the Document Shepherd have concerns that the document
          needs more review from a particular or broader perspective,
          e.g., security, operational complexity, someone familiar with
          AAA, internationalization, or XML?

No concerns.


   (1.d)  Does the Document Shepherd have any specific concerns or
          issues with this document that the Responsible Area Director
          and/or the IESG should be aware of?  For example, perhaps he
          or she is uncomfortable with certain parts of the document, or
          has concerns whether there really is a need for it.  In any
          event, if the WG has discussed those issues and has indicated
          that it still wishes to advance the document, detail those
          concerns here.  Has an IPR disclosure related to this document
          been filed?  If so, please include a reference to the
          disclosure and summarize the WG discussion and conclusion on
          this issue.

There have been concerns that the procedures described in this document
might be used to predict a NAT's behavior, which would in turn modify
application behavior.  It has been found this is risky because NAT behavior 
is known to change.  Thus, this document is Experimental and also contains 
an Applicability section.  These two things have reduced the working 
group's concerns.


   (1.e)  How solid is the WG consensus behind this document?  Does it
          represent the strong concurrence of a few individuals, with
          others being silent, or does the WG as a whole understand and
          agree with it?

There is solid WG consensus behind this document; many of its procedures
are based on procedures in RFC3489.



   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
          discontent?  If so, please summarize the areas of conflict in
          separate email messages to the Responsible Area Director.  (It
          should be in a separate email because this questionnaire is
          entered into the ID Tracker.)

There has been no extreme discontent.


   (1.g)  Has the Document Shepherd personally verified that the
          document satisfies all ID nits?  (See
          http://www.ietf.org/ID-Checklist.html and
          http://tools.ietf.org/tools/idnits/.)  Boilerplate checks are
          not enough; this check needs to be thorough. 

Yes.

          Has the document
          met all formal review criteria it needs to, such as the MIB
          Doctor, media type, and URI type reviews? 

Yes.

          If the document
          does not already indicate its intended status at the top of
          the first page, please indicate the intended status here.

intended status: Experimental


   (1.h)  Has the document split its references into normative and
          informative?  Are there normative references to documents that
          are not ready for advancement or are otherwise in an unclear
          state?  If such normative references exist, what is the
          strategy for their completion?  Are there normative references
          that are downward references, as described in [RFC3967]?  If
          so, list these downward references to support the Area
          Director in the Last Call procedure for them [RFC3967].

All references are verified by the document shepherd, and are good.


   (1.i)  Has the Document Shepherd verified that the document's IANA
          Considerations section exists and is consistent with the body
          of the document?  If the document specifies protocol
          extensions, are reservations requested in appropriate IANA
          registries?  Are the IANA registries clearly identified?  If
          the document creates a new registry, does it define the
          proposed initial contents of the registry and an allocation
          procedure for future registrations?  Does it suggest a
          reasonable name for the new registry?  See [RFC2434].  If the
          document describes an Expert Review process, has the Document
          Shepherd conferred with the Responsible Area Director so that
          the IESG can appoint the needed Expert during IESG Evaluation?

The document registers some new STUN attributes, following the procedures
of draft-ietf-behave-rfc3489bis (which is the STUN Internet Draft).


   (1.j)  Has the Document Shepherd verified that sections of the
          document that are written in a formal language, such as XML
          code, BNF rules, MIB definitions, etc., validate correctly in
          an automated checker?

The document contains no formal language.


   (1.k)  The IESG approval announcement includes a Document
          Announcement Write-Up.  Please provide such a Document
          Announcement Write-Up.  Recent examples can be found in the
          "Action" announcements for approved documents.  The approval
          announcement contains the following sections:

          Technical Summary
             Relevant content can frequently be found in the abstract
             and/or introduction of the document.  If not, this may be
             an indication that there are deficiencies in the abstract
             or introduction.


This specification defines an experimental usage of the Simple
Traversal Underneath Network Address Translators (NAT) (STUN)
Protocol that discovers the presence and current behaviour of NATs
and firewalls between the STUN client and the STUN server.


          Working Group Summary
             Was there anything in the WG process that is worth noting?
             For example, was there controversy about particular points
             or were there decisions where the consensus was
             particularly rough?

The original intent was to publish this specification as Informational,
but the working group decided Experimental would be a better track in
order to more clearly convey the risky nature of attempting to 
determine a NAT's behavior.


          Document Quality
             Are there existing implementations of the protocol?  Have a
             significant number of vendors indicated their plan to
             implement the specification? 

Two vendors are known to implement it.


             Are there any reviewers that
             merit special mention as having done a thorough review,
             e.g., one that resulted in important changes or a
             conclusion that the document had no substantive issues? 

They are listed in the acknowledgements section.

             If
             there was a MIB Doctor, Media Type, or other Expert Review,
             what was its course (briefly)?  In the case of a Media Type
             Review, on what date was the request posted?

This document did not include such reviews.


          Personnel
             Who is the Document Shepherd for this document?

Dan Wing, dwing@cisco.com

             Who is the
             Responsible Area Director? 

Magnus Westerlund, magnus.westerlund@ericsson.com

             If the document requires IANA
             experts(s), insert 'The IANA Expert(s) for the registries
             in this document are <TO BE ADDED BY THE AD>.'

The IANA Expert(s) for the registries in this document are <TO BE ADDED BY THE
AD>.


------=_NextPart_000_0EBE_01C909FF.E32C46D0
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

------=_NextPart_000_0EBE_01C909FF.E32C46D0--



