
From zhengyli@cisco.com  Thu Jun 30 00:30:59 2011
Return-Path: <zhengyli@cisco.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59B8F21F86A4; Thu, 30 Jun 2011 00:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.969
X-Spam-Level: 
X-Spam-Status: No, score=-8.969 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gsiSLJoHcoGk; Thu, 30 Jun 2011 00:30:57 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id C69D821F869C; Thu, 30 Jun 2011 00:30:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=zhengyli@cisco.com; l=14340; q=dns/txt; s=iport; t=1309419057; x=1310628657; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=m1oJffSywAc2r1JKOPPATBFeUitOq3e7Y1YP4CHM5JU=; b=B3NVfwv7hWlZIxaF9UvL2Xr7vBviQBD9mx2Tya4GMAH0Rwws37EZavSy t/ojatoHBdibPrnmuhPCxp99m3C0WuU3sYUliPsx4hGBJRPp7pfrw4uE+ 6Ylxlcn7CpsBUZxb+UslPKW87Kk479aUdS0k7a0Wyzaex9888opraheU4 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPwkDE5Io8UR/2dsb2JhbABSp013qiqeDIYwBIc4imuEdYtD
X-IronPort-AV: E=Sophos;i="4.65,449,1304294400"; d="scan'208";a="98948280"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-1.cisco.com with ESMTP; 30 Jun 2011 07:30:50 +0000
Received: from [64.104.167.59] ([64.104.167.59]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5U7UgBU014117; Thu, 30 Jun 2011 07:30:44 GMT
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Thu, 30 Jun 2011 15:30:38 +0800
Subject: Re: [BEHAVE] FW: Last Call: <draft-ietf-behave-ftp64-10.txt> (An FTP ALG for IPv6-to-IPv4 translation) to Proposed Standard
From: Rockson Li <zhengyli@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>, David Harrington <ietfdbh@comcast.net>
Message-ID: <CA324709.23D0F%zhengyli@cisco.com>
Thread-Topic: [BEHAVE] FW: Last Call: <draft-ietf-behave-ftp64-10.txt> (An FTP ALG for IPv6-to-IPv4 translation) to Proposed Standard
In-Reply-To: <817780D4-1CF0-4A5A-90A8-E8BF98A2274F@muada.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Fri, 01 Jul 2011 08:08:07 -0700
Cc: draft-ietf-behave-ftp64@tools.ietf.org, fgont@acm.org, "behave@ietf.orgWG WG" <behave@ietf.org>, Pekka Savola <pekkas@netcore.fi>, TSV Area <tsv-area@ietf.org>, "behave-chairs@tools.ietf.org Chairs" <behave-chairs@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-behave-ftp64.all@tools.ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 07:30:59 -0000

|The document does not mention or discuss LPRT and LPSV. Is that
intentional?
|The IANA registry says these are now obsolete, but RFC1639 is still
|experimental and no document has (formally) obsoleted these.


[RL] It looks like sec 2.5 of RFC5797 has obsoleted those two commands.


Regards,
-Rockson

On 6/28/11 12:17 AM, "Iljitsch van Beijnum" <iljitsch@muada.com> wrote:

>FTP ALG implementers: please respond if you have an opinion, some stuff
>below may make your life harder! (This is a response to two different
>messages.)
>
>On 3 jun 2011, at 14:06, David Harrington wrote:
>
>> Can you address these issues?
>> Do you have any other comments you know of that need to be included in
>> a new rev?
>
>There were three reviews. See below for two, I'm trying to clear
>something up about the other more directly.
>
>On 30 mei 2011, at 11:10, Pekka Savola wrote:
>
>> This is an ops-dir review of draft-ietf-behave-ftp64-10.
>
>> substantial comments
>> --------------------
>
>> The document does not mention or discuss LPRT and LPSV. Is that
>>intentional?
>> The IANA registry says these are now obsolete, but RFC1639 is still
>> experimental and no document has (formally) obsoleted these.
>
>I managed to overlook RFC 1639, and it wasn't brought up by anyone else
>during the process. Apparently wu-ftpd implements this and curl used to,
>but both failed to see any real-world usage so I think we can ignore this
>without creating problems.
>
>>   Telnet option negotiation attempts by either the client or the
>>   server, except for those allowed by [RFC1123], MUST be rejected by
>>   the FTP ALG without relaying those attempts.  This avoids the
>>   situation where the client and the server negotiate Telnet options
>>   that are unimplemented by the FTP ALG.
>
>> ... what does "rejected" mean exactly?  Does the ALG send back to
>> the negotiation attempter some error code?  Does it abort the
>>connection?
>> ignore these options?  strip them out when connecting to the other end?
>
>What I had in mind was reply with a "DON'T". Is this text more clear?
>
>  Telnet option negotiation attempts by either the client or the
>  server, except for those allowed by [RFC1123], MUST be rejected by
>  the FTP ALG without relaying those attempts. For the purpose of
>  Telnet option negotiation, an FTP ALG MUST follow the behavior of
>  an FTP server as specified in [RFC1123] section 4.1.2.12. This...
>
>That section says:
>
>         4.1.2.12  Connections: RFC-959 Section 5.2
>
>            The words "and the port used" in the second paragraph of
>            this section of RFC-959 are erroneous (historical), and they
>            should be ignored.
>
>            On a multihomed server host, the default data transfer port
>            (L-1) MUST be associated with the same local IP address as
>            the corresponding control connection to port L.
>
>            A user-FTP MUST NOT send any Telnet controls other than
>            SYNCH and IP on an FTP control connection. In particular, it
>            MUST NOT attempt to negotiate Telnet options on the control
>            connection.  However, a server-FTP MUST be capable of
>            accepting and refusing Telnet negotiations (i.e., sending
>            DONT/WONT).
>
>            DISCUSSION:
>                 Although the RFC says: "Server- and User- processes
>                 should follow the conventions for the Telnet
>                 protocol...[on the control connection]", it is not the
>                 intent that Telnet option negotiation is to be
>                 employed.
>
>> 8. Default port 20 translation
>
>>   If the client does not issue an EPSV/PASV or EPRT/PORT command prior
>>   to initiating a file transfer, it is invoking the default active FTP
>>   behavior where the server sets up a TCP session towards the client.
>>   In this situation, the source port number is the default FTP data
>>   port (port 20) and the destination port is the port the client uses
>>   as the source port for the control channel session.
>
>> .. is it?  I thought the source port used by the server is orthogonal to
>> whether pasv/port is issued.  AFAIK, multiple FTP server implementations
>> never use port 20.  But I have not recently tested this myself.
>
>RFC 959:
>
>   3.2.  ESTABLISHING DATA CONNECTIONS
>
>      The mechanics of transferring data consists of setting up the data
>      connection to the appropriate ports and choosing the parameters
>      for transfer.  Both the user and the server-DTPs have a default
>      data port.  The user-process default data port is the same as the
>      control connection port (i.e., U).  The server-process default
>      data port is the port adjacent to the control connection port
>      (i.e., L-1).
>
>>   The ALG MUST enable or disable EPSV to PASV translation as requested.
>>   If EPRT to PORT translation is supported, ALGS ENABLE64 SHOULD enable
>>   it and ALGS DISABLE64 SHOULD disable it along with enabling or
>>   disabling EPSV to PASV translation, respectively.  If EPRT to PORT
>>   translation is not supported, ALGS ENABLE64 only enables EPSV to PASV
>>   translation.
>
>> .. what does this SHOULD..along with.. mean?  I read it so that it's OK
>> that for "ALGS DISABLE64" EPSV->PASV is disabled but EPRT->PORT is not
>> disabled?  A different way to read it would be that both EPSV->PASV and
>> EPRT->PORT are SHOULDs.
>
>I think what it says is that it's optional to disable PORT->EPRT upon
>DISABLE64. Enabling is optional because the feature is optional, but I
>guess if you have the feature disabling should be mandatory, so
>SHOULD->MUST:
>
>  The ALG MUST enable or disable EPSV to PASV translation as requested.
>  If EPRT to PORT translation is supported, ALGS ENABLE64 MUST enable
>  it and ALGS DISABLE64 MUST disable it along with...
>
>Agree?
>
>>   A survey done in April of 2009 of 25 randomly picked and/or well-
>>   known FTP sites reachable over IPv4 showed that only 12 of them
>>   supported EPSV over IPv4.
>
>> .. fwiw, Dan Wing redid this test on 18 May 2011, reporting on behave
>>list.
>> the results didn't differ much (I didn't look at the numbers), but if
>>you
>> want to update this, now would be the chance.
>
>I don't see the need to.
>
>> If
>>   such a multi-purpose ALG forbids the use of the AUTH command for
>>   policy reasons, the side effect of making the ALG stop performing the
>>   translations described here, as well as other possible interventions
>>   related to IPv6-to-IPv4 translation, MUST be retained even if the ALG
>>   responds to the AUTH command with an error and does not propagate the
>>   command to the server.
>
>> .. I had a hard time following what this one sentence includign a MUST
>> actually requires.  Maybe break down to more easily digestible
>>sentences?
>
>What about this:
>
>If such a multi-purpose ALG forbids the use of the AUTH command for
>policy reasons, the side effect of the AUTH command as described in this
>document MUST be retained. In other words, if the ALG does not propagate
>the AUTH command to the server, the ALG MUST still stop all possible
>interventions related to IPv6-to-IPv4 translation. This is true for the
>remaining duration
>of the control channel session, and applies even if the ALG
>responds to the AUTH command with an error.
>
>>   [Bernstein]
>>              Bernstein, D., "PASV security and PORT security", 2000,
>>              <http://cr.yp.to/ftp/security.html>.
>
>> .. this reference is not cited in the doc, add or remove?
>
>I'll remove it.
>
>
>On 4 jun 2011, at 0:16, Fernando Gont wrote:
>
>> I've reviewed this document as part of the transport area directorate's
>> ongoing effort to review key IETF documents.
>
>
>> * Section 1, page 3:
>>   In 5 cases, issuing the EPSV
>>   command to the server led to a significant delay, in 3 cases followed
>>   by a control channel reset.
>
>> Could you please clarify what was the cause of the delay? And, btw, have
>> you guys put the details of your results publicly available somewhere?
>
>What about the following text:
>
>Due to lack of additional information, it is impossible to determine
>conclusively why certain FTP servers reset the control channel connection
>some time after issueing an EPSV command. However, a reasonable
>explanation would be that these FTP servers are located behind
>application-aware firewalls which monitor the control channel session and
>only allow the creation of data channel sessions to the ports listed in
>the responses to PASV (and maybe PORT) commands. As the response to an
>EPSV command is different (a 229 code rather than a 227 code), a firewall
>that is unaware of the EPSV command would block the subsequent data
>channel setup attempt, after which the FTP server may decide to terminate
>the control channel session which isn't progressing the way it should.
>
>> * Section 1, page 3-4:
>>   Clients that want to engage in more complex behavior, such as server-
>>   to-server transfers, may make an FTP application layer gateway (ALG)
>>   go into transparent mode by issuing AUTH or ALGS commands as
>>   explained in Section 5.
>
>> I thought server-to-server transfer had been banned for many years now
>> (it was exploited for address scan purposes). Am I missing something?
>
>Do you have a reference?
>
>As it's only listed here as an example of something that isn't addressed,
>I don't think it's an issue to include this here.
>
>> * Section 5:
>>   In the second case, an implementation MUST have the ability to track
>>   and update TCP sequence numbers when translating packets as well as
>>   the ability to break up packets into smaller packets after
>> [....]
>
>> What about the TCP URG flag and the Urgent Pointer? FTP is one of the
>> few legacy applications that make use of TCP's urgent mode. And while
>> use in new applications is deprecated, and TCP urgent mode itself is
>> unreliable (see RFC 6093), you should make an explicit decision about
>> what to do with TCP urgent mode when used for the FTP control channel.
>
>The word "urgent" isn't mentioned in RFC 959 or the FTP-related part of
>RFC 1123. But RFC 959 does mention using the Telnet SYNCH signal, which
>involves using urgent data. However, it looks like it's legal to ignore
>the urgent pointer, from RFC 793:
>
>  TCP also provides a means to communicate to the receiver of data that
>  at some point further along in the data stream than the receiver is
>  currently reading there is urgent data.  TCP does not attempt to
>  define what the user specifically does upon being notified of pending
>  urgent data, but the general notion is that the receiving process will
>  take action to process the urgent data quickly
>
>> When packets are translated individually, the ALG should update the
>> Urgent Pointer if/where necessary. If the ALG terminates the IPv6 TCP
>> session, there's the question of whether urgent mode should be "copied"
>> from the IPv6 session to the IPv4 session.
>
>I think it's not worth the trouble and unlikely to be tested well, so I
>would be in favor of clearing the URG flag. Any objections?
>
>> * Section 5.1, page 7:
>> For the time being, ALG implementations may employ
>>   one of the following strategies regarding LANG negotiation
>
>> Should you s/may/MAY/?
>
>Not really. I'll see what the RFC Editor says.
>
>> * Section 5.1, page 8:
>>   3.  Block LANG negotiation by translating the LANG command to a NOOP
>>       command, and translating the resulting 200 response into a
>>       response appropriate for unsupported commands, such as 500.  Text
>>       is sent in the default language.
>
>> I think you should mandate which exact code the 200 should be translated
>> to, rather than just provide an example.
>
>Let's make it a 502 then.
>
>>   The File Transfer Protocol (FTP) has a very long history, and despite
>>   the fact that today, other options exist to perform file transfers,
>>   FTP is still in common use.
>
>> Remove the comma between "today" and "others"
>
>Ok.
>
>>   translators
>>   are used to bridge that gap, FTP is made to work through these
>>   translators as best it can.
>
>> s/as best as it can/to the best possible extent/?
>
>Why not.
>
>> * Section 5.1 (page 7) and elsewhere:
>>   So the situation where the client and server try to
>>   negotiate a language that the ALG doesn't support can't be avoided.
>
>> Expand doesn't to "does not", "can't" to "cannot", etc.
>
>Hm, the 425 code has "can't" in it. I'll leave this open and see what the
>RFC Editor says.
>
>> * Section 5.1, page 8:
>>   Note that [RFC2640] section 3.1 specifies new handling for spaces and
>>   the CR character in path names.
>
>> Rephrase to "Note that Section 3.1 of [RFC2640]..."
>
>I adopted the word order but not the capitalization.
>
>> * Section 11, page 12:
>>   ALGs MUST support the new ALGS (ALG status) command that allows
>>   command MUST be passed on to the server without modification, and the
>>   clients to query and set the ALG's status.
>
>> I had trouble parsing this sentence.
>
>This is the text that is in -10:
>
>  ALGs MUST support the new ALGS (ALG status) command that allows
>  clients to query and set the ALG's status.  FTP servers (as opposed
>  to ALGs) MUST NOT perform any actions upon receiving the ALGS
>  command. FTP servers MUST still send a response, however.
>  If FTP servers recognize the ALGS command, the best course
>  of action would be to return a 202 response:
>
>Apparently two lines got lost at your end.
>
>> * Section 11, page 12:
>>   A client can use the ALGS command to request the ALG's status and to
>>   enable and disable EPSV to PASV and, if implemented, EPRT to PORT
>>   translation.
>
>> Please rephrase to "...disable EPSV to PASV translation and, if
>> implemented, EPRT to PORT translation".
>
>Ok.
>
>Both of you, thanks for the reviews.
>_______________________________________________
>Behave mailing list
>Behave@ietf.org
>https://www.ietf.org/mailman/listinfo/behave



From zhengyli@cisco.com  Thu Jun 30 00:31:00 2011
Return-Path: <zhengyli@cisco.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADEB21F869C; Thu, 30 Jun 2011 00:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.669
X-Spam-Level: 
X-Spam-Status: No, score=-8.669 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_HI=-8, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90meHGiTFoMH; Thu, 30 Jun 2011 00:30:58 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE0621F86A5; Thu, 30 Jun 2011 00:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=zhengyli@cisco.com; l=14669; q=dns/txt; s=iport; t=1309419056; x=1310628656; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=v9hbqJ5geZg2YJS11T/NN5K8MmfUPU5yoLqnpQnQ9GY=; b=CxjO915F/In6zwlGmOrQBQGbYseXc39tb0ptP/DPhTvu9rvKqTt71kSe Ryrf1l92EwgdS0CY5oceNhfEMR31kwX5L6mhT4QgsA4/BAMu9yEZ543y5 yaTJSlBr82XE7GZ6Oq3VinyD1zYGmCVYLIK9rJniHHytOBm7zIiCjipQQ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPwkDE5Io8UR/2dsb2JhbABSp013qiqeDIYwBIc4imuEdYtD
X-IronPort-AV: E=Sophos;i="4.65,449,1304294400"; d="scan'208";a="39960118"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-2.cisco.com with ESMTP; 30 Jun 2011 07:30:51 +0000
Received: from [64.104.167.59] ([64.104.167.59]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5U7UgBV014117; Thu, 30 Jun 2011 07:30:49 GMT
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Thu, 30 Jun 2011 15:30:41 +0800
Subject: Re: [BEHAVE] FW: Last Call: <draft-ietf-behave-ftp64-10.txt> (An FTP ALG for IPv6-to-IPv4 translation) to Proposed Standard
From: Rockson Li <zhengyli@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>, David Harrington <ietfdbh@comcast.net>
Message-ID: <CA2FA7DD.2367A%zhengyli@cisco.com>
Thread-Topic: [BEHAVE] FW: Last Call: <draft-ietf-behave-ftp64-10.txt> (An FTP ALG for IPv6-to-IPv4 translation) to Proposed Standard
In-Reply-To: <817780D4-1CF0-4A5A-90A8-E8BF98A2274F@muada.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Fri, 01 Jul 2011 08:08:07 -0700
Cc: draft-ietf-behave-ftp64@tools.ietf.org, fgont@acm.org, "behave@ietf.orgWG WG" <behave@ietf.org>, Pekka Savola <pekkas@netcore.fi>, TSV Area <tsv-area@ietf.org>, "behave-chairs@tools.ietf.org Chairs" <behave-chairs@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-behave-ftp64.all@tools.ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 07:31:00 -0000

|The document does not mention or discuss LPRT and LPSV. Is that
intentional?
|The IANA registry says these are now obsolete, but RFC1639 is still
|experimental and no document has (formally) obsoleted these.


[RL] It looks like sec 2.5 of RFC5797 has obsoleted those two commands.

On  ".. is it?  I thought the source port used by the server is orthogonal
to
whether pasv/port is issued.  AFAIK, multiple FTP server implementations
never use port 20.  But I have not recently tested this myself.
"

I think David was asking,do we need to assume the source port 20 from ftp
server for data connection would be always true if

On 6/28/11 12:17 AM, "Iljitsch van Beijnum" <iljitsch@muada.com> wrote:

>FTP ALG implementers: please respond if you have an opinion, some stuff
>below may make your life harder! (This is a response to two different
>messages.)
>
>On 3 jun 2011, at 14:06, David Harrington wrote:
>
>> Can you address these issues?
>> Do you have any other comments you know of that need to be included in
>> a new rev?
>
>There were three reviews. See below for two, I'm trying to clear
>something up about the other more directly.
>
>On 30 mei 2011, at 11:10, Pekka Savola wrote:
>
>> This is an ops-dir review of draft-ietf-behave-ftp64-10.
>
>> substantial comments
>> --------------------
>
>> The document does not mention or discuss LPRT and LPSV. Is that
>>intentional?
>> The IANA registry says these are now obsolete, but RFC1639 is still
>> experimental and no document has (formally) obsoleted these.
>
>I managed to overlook RFC 1639, and it wasn't brought up by anyone else
>during the process. Apparently wu-ftpd implements this and curl used to,
>but both failed to see any real-world usage so I think we can ignore this
>without creating problems.
>
>>   Telnet option negotiation attempts by either the client or the
>>   server, except for those allowed by [RFC1123], MUST be rejected by
>>   the FTP ALG without relaying those attempts.  This avoids the
>>   situation where the client and the server negotiate Telnet options
>>   that are unimplemented by the FTP ALG.
>
>> ... what does "rejected" mean exactly?  Does the ALG send back to
>> the negotiation attempter some error code?  Does it abort the
>>connection?
>> ignore these options?  strip them out when connecting to the other end?
>
>What I had in mind was reply with a "DON'T". Is this text more clear?
>
>  Telnet option negotiation attempts by either the client or the
>  server, except for those allowed by [RFC1123], MUST be rejected by
>  the FTP ALG without relaying those attempts. For the purpose of
>  Telnet option negotiation, an FTP ALG MUST follow the behavior of
>  an FTP server as specified in [RFC1123] section 4.1.2.12. This...
>
>That section says:
>
>         4.1.2.12  Connections: RFC-959 Section 5.2
>
>            The words "and the port used" in the second paragraph of
>            this section of RFC-959 are erroneous (historical), and they
>            should be ignored.
>
>            On a multihomed server host, the default data transfer port
>            (L-1) MUST be associated with the same local IP address as
>            the corresponding control connection to port L.
>
>            A user-FTP MUST NOT send any Telnet controls other than
>            SYNCH and IP on an FTP control connection. In particular, it
>            MUST NOT attempt to negotiate Telnet options on the control
>            connection.  However, a server-FTP MUST be capable of
>            accepting and refusing Telnet negotiations (i.e., sending
>            DONT/WONT).
>
>            DISCUSSION:
>                 Although the RFC says: "Server- and User- processes
>                 should follow the conventions for the Telnet
>                 protocol...[on the control connection]", it is not the
>                 intent that Telnet option negotiation is to be
>                 employed.
>
>> 8. Default port 20 translation
>
>>   If the client does not issue an EPSV/PASV or EPRT/PORT command prior
>>   to initiating a file transfer, it is invoking the default active FTP
>>   behavior where the server sets up a TCP session towards the client.
>>   In this situation, the source port number is the default FTP data
>>   port (port 20) and the destination port is the port the client uses
>>   as the source port for the control channel session.
>
>> .. is it?  I thought the source port used by the server is orthogonal to
>> whether pasv/port is issued.  AFAIK, multiple FTP server implementations
>> never use port 20.  But I have not recently tested this myself.
>
>RFC 959:
>
>   3.2.  ESTABLISHING DATA CONNECTIONS
>
>      The mechanics of transferring data consists of setting up the data
>      connection to the appropriate ports and choosing the parameters
>      for transfer.  Both the user and the server-DTPs have a default
>      data port.  The user-process default data port is the same as the
>      control connection port (i.e., U).  The server-process default
>      data port is the port adjacent to the control connection port
>      (i.e., L-1).
>
>>   The ALG MUST enable or disable EPSV to PASV translation as requested.
>>   If EPRT to PORT translation is supported, ALGS ENABLE64 SHOULD enable
>>   it and ALGS DISABLE64 SHOULD disable it along with enabling or
>>   disabling EPSV to PASV translation, respectively.  If EPRT to PORT
>>   translation is not supported, ALGS ENABLE64 only enables EPSV to PASV
>>   translation.
>
>> .. what does this SHOULD..along with.. mean?  I read it so that it's OK
>> that for "ALGS DISABLE64" EPSV->PASV is disabled but EPRT->PORT is not
>> disabled?  A different way to read it would be that both EPSV->PASV and
>> EPRT->PORT are SHOULDs.
>
>I think what it says is that it's optional to disable PORT->EPRT upon
>DISABLE64. Enabling is optional because the feature is optional, but I
>guess if you have the feature disabling should be mandatory, so
>SHOULD->MUST:
>
>  The ALG MUST enable or disable EPSV to PASV translation as requested.
>  If EPRT to PORT translation is supported, ALGS ENABLE64 MUST enable
>  it and ALGS DISABLE64 MUST disable it along with...
>
>Agree?
>
>>   A survey done in April of 2009 of 25 randomly picked and/or well-
>>   known FTP sites reachable over IPv4 showed that only 12 of them
>>   supported EPSV over IPv4.
>
>> .. fwiw, Dan Wing redid this test on 18 May 2011, reporting on behave
>>list.
>> the results didn't differ much (I didn't look at the numbers), but if
>>you
>> want to update this, now would be the chance.
>
>I don't see the need to.
>
>> If
>>   such a multi-purpose ALG forbids the use of the AUTH command for
>>   policy reasons, the side effect of making the ALG stop performing the
>>   translations described here, as well as other possible interventions
>>   related to IPv6-to-IPv4 translation, MUST be retained even if the ALG
>>   responds to the AUTH command with an error and does not propagate the
>>   command to the server.
>
>> .. I had a hard time following what this one sentence includign a MUST
>> actually requires.  Maybe break down to more easily digestible
>>sentences?
>
>What about this:
>
>If such a multi-purpose ALG forbids the use of the AUTH command for
>policy reasons, the side effect of the AUTH command as described in this
>document MUST be retained. In other words, if the ALG does not propagate
>the AUTH command to the server, the ALG MUST still stop all possible
>interventions related to IPv6-to-IPv4 translation. This is true for the
>remaining duration
>of the control channel session, and applies even if the ALG
>responds to the AUTH command with an error.
>
>>   [Bernstein]
>>              Bernstein, D., "PASV security and PORT security", 2000,
>>              <http://cr.yp.to/ftp/security.html>.
>
>> .. this reference is not cited in the doc, add or remove?
>
>I'll remove it.
>
>
>On 4 jun 2011, at 0:16, Fernando Gont wrote:
>
>> I've reviewed this document as part of the transport area directorate's
>> ongoing effort to review key IETF documents.
>
>
>> * Section 1, page 3:
>>   In 5 cases, issuing the EPSV
>>   command to the server led to a significant delay, in 3 cases followed
>>   by a control channel reset.
>
>> Could you please clarify what was the cause of the delay? And, btw, have
>> you guys put the details of your results publicly available somewhere?
>
>What about the following text:
>
>Due to lack of additional information, it is impossible to determine
>conclusively why certain FTP servers reset the control channel connection
>some time after issueing an EPSV command. However, a reasonable
>explanation would be that these FTP servers are located behind
>application-aware firewalls which monitor the control channel session and
>only allow the creation of data channel sessions to the ports listed in
>the responses to PASV (and maybe PORT) commands. As the response to an
>EPSV command is different (a 229 code rather than a 227 code), a firewall
>that is unaware of the EPSV command would block the subsequent data
>channel setup attempt, after which the FTP server may decide to terminate
>the control channel session which isn't progressing the way it should.
>
>> * Section 1, page 3-4:
>>   Clients that want to engage in more complex behavior, such as server-
>>   to-server transfers, may make an FTP application layer gateway (ALG)
>>   go into transparent mode by issuing AUTH or ALGS commands as
>>   explained in Section 5.
>
>> I thought server-to-server transfer had been banned for many years now
>> (it was exploited for address scan purposes). Am I missing something?
>
>Do you have a reference?
>
>As it's only listed here as an example of something that isn't addressed,
>I don't think it's an issue to include this here.
>
>> * Section 5:
>>   In the second case, an implementation MUST have the ability to track
>>   and update TCP sequence numbers when translating packets as well as
>>   the ability to break up packets into smaller packets after
>> [....]
>
>> What about the TCP URG flag and the Urgent Pointer? FTP is one of the
>> few legacy applications that make use of TCP's urgent mode. And while
>> use in new applications is deprecated, and TCP urgent mode itself is
>> unreliable (see RFC 6093), you should make an explicit decision about
>> what to do with TCP urgent mode when used for the FTP control channel.
>
>The word "urgent" isn't mentioned in RFC 959 or the FTP-related part of
>RFC 1123. But RFC 959 does mention using the Telnet SYNCH signal, which
>involves using urgent data. However, it looks like it's legal to ignore
>the urgent pointer, from RFC 793:
>
>  TCP also provides a means to communicate to the receiver of data that
>  at some point further along in the data stream than the receiver is
>  currently reading there is urgent data.  TCP does not attempt to
>  define what the user specifically does upon being notified of pending
>  urgent data, but the general notion is that the receiving process will
>  take action to process the urgent data quickly
>
>> When packets are translated individually, the ALG should update the
>> Urgent Pointer if/where necessary. If the ALG terminates the IPv6 TCP
>> session, there's the question of whether urgent mode should be "copied"
>> from the IPv6 session to the IPv4 session.
>
>I think it's not worth the trouble and unlikely to be tested well, so I
>would be in favor of clearing the URG flag. Any objections?
>
>> * Section 5.1, page 7:
>> For the time being, ALG implementations may employ
>>   one of the following strategies regarding LANG negotiation
>
>> Should you s/may/MAY/?
>
>Not really. I'll see what the RFC Editor says.
>
>> * Section 5.1, page 8:
>>   3.  Block LANG negotiation by translating the LANG command to a NOOP
>>       command, and translating the resulting 200 response into a
>>       response appropriate for unsupported commands, such as 500.  Text
>>       is sent in the default language.
>
>> I think you should mandate which exact code the 200 should be translated
>> to, rather than just provide an example.
>
>Let's make it a 502 then.
>
>>   The File Transfer Protocol (FTP) has a very long history, and despite
>>   the fact that today, other options exist to perform file transfers,
>>   FTP is still in common use.
>
>> Remove the comma between "today" and "others"
>
>Ok.
>
>>   translators
>>   are used to bridge that gap, FTP is made to work through these
>>   translators as best it can.
>
>> s/as best as it can/to the best possible extent/?
>
>Why not.
>
>> * Section 5.1 (page 7) and elsewhere:
>>   So the situation where the client and server try to
>>   negotiate a language that the ALG doesn't support can't be avoided.
>
>> Expand doesn't to "does not", "can't" to "cannot", etc.
>
>Hm, the 425 code has "can't" in it. I'll leave this open and see what the
>RFC Editor says.
>
>> * Section 5.1, page 8:
>>   Note that [RFC2640] section 3.1 specifies new handling for spaces and
>>   the CR character in path names.
>
>> Rephrase to "Note that Section 3.1 of [RFC2640]..."
>
>I adopted the word order but not the capitalization.
>
>> * Section 11, page 12:
>>   ALGs MUST support the new ALGS (ALG status) command that allows
>>   command MUST be passed on to the server without modification, and the
>>   clients to query and set the ALG's status.
>
>> I had trouble parsing this sentence.
>
>This is the text that is in -10:
>
>  ALGs MUST support the new ALGS (ALG status) command that allows
>  clients to query and set the ALG's status.  FTP servers (as opposed
>  to ALGs) MUST NOT perform any actions upon receiving the ALGS
>  command. FTP servers MUST still send a response, however.
>  If FTP servers recognize the ALGS command, the best course
>  of action would be to return a 202 response:
>
>Apparently two lines got lost at your end.
>
>> * Section 11, page 12:
>>   A client can use the ALGS command to request the ALG's status and to
>>   enable and disable EPSV to PASV and, if implemented, EPRT to PORT
>>   translation.
>
>> Please rephrase to "...disable EPSV to PASV translation and, if
>> implemented, EPRT to PORT translation".
>
>Ok.
>
>Both of you, thanks for the reviews.
>_______________________________________________
>Behave mailing list
>Behave@ietf.org
>https://www.ietf.org/mailman/listinfo/behave



From david.black@emc.com  Tue Jul  5 07:29:38 2011
Return-Path: <david.black@emc.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4409E21F85F3; Tue,  5 Jul 2011 07:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.037
X-Spam-Level: 
X-Spam-Status: No, score=-104.037 tagged_above=-999 required=5 tests=[AWL=2.562, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RetrxpCpF+wp; Tue,  5 Jul 2011 07:29:37 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 480A221F8608; Tue,  5 Jul 2011 07:29:36 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p65ETLAC001552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jul 2011 10:29:22 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 5 Jul 2011 10:29:10 -0400
Received: from mxhub22.corp.emc.com (mxhub22.corp.emc.com [128.221.56.108]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p65ESYH3019126; Tue, 5 Jul 2011 10:28:34 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub22.corp.emc.com ([128.221.56.108]) with mapi; Tue, 5 Jul 2011 10:28:34 -0400
From: <david.black@emc.com>
To: <tsv-dir@ietf.org>, <tsv-area@ietf.org>, <ietf@ietf.org>, <c.raiciu@cs.ucl.ac.uk>, <m.handley@cs.ucl.ac.uk>, <d.wischik@cs.ucl.ac.uk>
Date: Tue, 5 Jul 2011 10:28:33 -0400
Subject: tsv-dir review of draft-ietf-mptcp-congestion-05
Thread-Topic: tsv-dir review of draft-ietf-mptcp-congestion-05
Thread-Index: Acw7H9G26311hfzYTG+iDWuKZd6Dmw==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05893924C1@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: multipathtcp@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 14:29:38 -0000

I've reviewed this document as part of the transport area directorate's ong=
oing
effort to review key IETF documents. These comments were written primarily =
for the
transport area directors, but are copied to the document's authors for thei=
r
information and to allow them to address any issues raised. The authors sho=
uld
consider this review together with any other last-call comments they receiv=
e.
Please always CC: tsv-dir@ietf.org if you reply to or forward this review.

Summary:

This draft is on the right track but has open issues, described in the revi=
ew.

Comments:

This draft specifies the congestion control modifications for multi-path TC=
P.

Major:

I have one open issue - the first two goals (in the Introduction) are to ha=
ve multipath
TCP connections behave somewhat like single-path connections in terms of ef=
fects on
(fairness to) other traffic.  The algorithm specified accomplishes this sol=
ely by
coupling the additive increase functionality across the flows, but allowing=
 each flow
to react to drops and congestion separately (no decrease coupling).  The dr=
aft does
not explain why increase coupling along is sufficient to achieve these goal=
s or what
compromise to the goals results from only coupling increases.

Section 5 is a good start on this discussion, but it's not clear about what=
 compromises
to the goals results from increase coupling only.  Section 5 criticizes an =
alternative
that couples both increases and decreases for failing to achieve Goal 1, bu=
t doesn't
say what this approach achieves.  At most a few additional sentences in Sec=
tion 5 should
suffice to address this concern, and Section 2 should be edited to align wi=
th the
changes to Section 5.

Minor:

While the [NSDI] paper is a fine place to reference work published in confe=
rences
and/or journals, RFC 3124 on the Congestion Manager is related IETF work an=
d should
be cited here as an Informative Reference.

idnits 2.12.12 didn't find any nits.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From stbryant@cisco.com  Wed Jul  6 07:15:32 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAF2621F85A7; Wed,  6 Jul 2011 07:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.599
X-Spam-Level: 
X-Spam-Status: No, score=-109.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, GB_MUTUALBENEFIT=2, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvjs66umHkkv; Wed,  6 Jul 2011 07:15:31 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8861721F84EB; Wed,  6 Jul 2011 07:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=4009; q=dns/txt; s=iport; t=1309961730; x=1311171330; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=DUd7o9+p2p3D7Iu9viFzVbltTKBr1R2vcs/movTM2js=; b=DOHN+V71BosdwpA0iiACLAPgT8Gn/8uoWEenXSOA06+ly/G1NSQGv7Vt 0kukqBTq1gDf0uTFaGxu8zmllMASAEKRUCzgOqtjWgSF8LSU9wZClQNCs DTnLsylidTm+Z9fCrYnitpz86RJ3gg1wkoEs6zjLv//NKhtmbpGkiM5zr s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EANlsFE6Q/khL/2dsb2JhbABFDqgDd4h6pQODFQ8Bmw2DIYMVBJJBkD0
X-IronPort-AV: E=Sophos;i="4.65,487,1304294400"; d="scan'208";a="40865394"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 06 Jul 2011 14:15:29 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p66EFT6S009462; Wed, 6 Jul 2011 14:15:29 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-77.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p66EFS6m016947; Wed, 6 Jul 2011 15:15:28 +0100 (BST)
Message-ID: <4E146E49.9050403@cisco.com>
Date: Wed, 06 Jul 2011 15:16:41 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Rolf Winter <Rolf.Winter@neclab.eu>
Subject: Re: tsv-dir review of draft-ietf-pwe3-fat-pw-06
References: <791AD3077F94194BB2BDD13565B6295D05E6A0F3@PALLENE.office.hd>
In-Reply-To: <791AD3077F94194BB2BDD13565B6295D05E6A0F3@PALLENE.office.hd>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 06 Jul 2011 08:06:34 -0700
Cc: "draft-ietf-pwe3-fat-pw@tools.ietf.org" <draft-ietf-pwe3-fat-pw@tools.ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsv-dir@ietf.org" <tsv-dir@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 14:15:32 -0000

Rolf

Thank you for the review

On 19/05/2011 14:24, Rolf Winter wrote:
>
>
> CONTENT:
>
> Section 3 says:
> "If a flow LSE is present, it MUST be checked to determine whether it
> carries a reserved label.  If it is a reserved label the packet is
> processed according to the rules associated with that reserved label,
> otherwise the LSE is discarded."
> However section 1.2 states:
> "Note that the flow label MUST NOT be an MPLS reserved label."
> Isn't that a contradiction to a certain extend. I mean, if there is a reserved label in the flow LSE, isn't that an error and should not be processed?

Section 1.2 is saying that the flow label generator MUST NOT generate 
and apply a reserved label.

Section 3 is saying that if there is a label put in that position it 
must have been
put there by some application that wanted a diagnostic so process it.

The intent is careful what you send, liberal with what you receive.

>
> section 8.4:
> The second bullet in the section under: "The issues described above are mitigated by the following two factors:". I wonder whether that isn't a bit farfetched. I mean, in principle you suggest that customers could change e.g. the way their applications behave to let the ingress PE to be able to better apply the flow label. That sounds like asking a customer to change something on their application end to have a better network connectivity.

This is dealing with the single large flow case. There is no way to load 
balance a single large flow at the speeds we need to operate and at the 
price performance point needed. This is noting that the customer needs 
to help out.

Clearly if the user is unable to modify their application they get the 
performance they get, and indeed risk running foul of ingress policing 
by the provider.

  section 8.5. Isn't a bigger problem here that you cannot guarantee 
that the OAM packets follow the same ECMP path and that violates the 
fate sharing requirement?

I added:

"In addition MPLS-TP makes extensive use of the fate sharing between OAM 
and data packets, which is defeated by the flow LSE."
>
> section 12:
> You essentially say that the behaviour of IP packets are well defined regarding congestion and nothing needs to be done. Other payload needs to be dealt with by PW congestion avoidance (whatever that means). So IP packets that are not reacting to congestion (such as UDP) are no concern but other packets with the same behaviour are? Is that a correct reading of the text?
Yes. The PW assumes that all IP packets are as well behaved as the IETF 
requires them to be. It is not the job of PWE3 to specify or influence 
the congestion behavior of IP packets, we just carry them as a "wire" would.



>
> section 2:
> s/identify flows/identifies flows/
I am not sure. Let's leave it to RFCed.
>
>
> section 8.4:
> Option one says: "The operator can choose to do nothing and the system will work as it does without the flow label."
> Isn't this option to not use the flow label. If so a better wording would maybe be: "The operator can choose to do nothing, i.e. to not employ the flow label"
The point is that the operator would prefer for their own reasons to see 
load balancing so they probably want to turn it on and hope that at some 
future stage the user modifies their profile to the mutual benefit of 
user and provider.

The do nothing refers to taking no further action.

> Option 3: 2/flows,/flows./
>
> Why is section 9 not section 8.7? I mean it is concerned with applicability which is what section 8 is about.
PWS are not LSPs and there is work on this WRT LSPs in MPLS WG. This is 
a heads up that this other work is happening, that both parties are 
aware of what the other is doing. It seems reasonable to put it in its 
own section.

>
> section 9:
>
> s/This is can be regarded as/This can be regarded as/
This section was re-written following genart f/b from Mary Barns.

Regards

Stewart

From wes@mti-systems.com  Thu Jul  7 12:15:13 2011
Return-Path: <wes@mti-systems.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3F91F0CD6 for <tsv-area@ietfa.amsl.com>; Thu,  7 Jul 2011 12:15:13 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UhYDZPsMpb4s for <tsv-area@ietfa.amsl.com>; Thu,  7 Jul 2011 12:15:10 -0700 (PDT)
Received: from omr10.networksolutionsemail.com (omr10.networksolutionsemail.com [205.178.146.60]) by ietfa.amsl.com (Postfix) with ESMTP id D7A8F1F0CCC for <tsv-area@ietf.org>; Thu,  7 Jul 2011 12:15:09 -0700 (PDT)
Received: from cm-omr3 (mail.networksolutionsemail.com [205.178.146.50]) by omr10.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p67JF78i027077 for <tsv-area@ietf.org>; Thu, 7 Jul 2011 15:15:07 -0400
Authentication-Results: cm-omr3 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [107.45.108.183] ([107.45.108.183:56015] helo=[192.168.9.2]) by cm-omr3 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 55/07-28066-AB5061E4; Thu, 07 Jul 2011 15:15:07 -0400
Message-ID: <4E1605BC.40603@mti-systems.com>
Date: Thu, 07 Jul 2011 15:15:08 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: tsv-area@ietf.org
Subject: TSVAREA meeting at IETF81
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2011 19:15:13 -0000

Hi, we're planning to have a TSVAREA meeting at the upcoming
IETF 81 meeting in Quebec City.

A draft agenda is at:
http://www.ietf.org/proceedings/81/agenda/tsvarea.txt

Please let David and I know if there are any additional topics
we might need to plan for (tsv-ads@tools.ietf.org).

-- 
Wes Eddy
MTI Systems

From ietfdbh@comcast.net  Tue Jul 12 13:13:23 2011
Return-Path: <ietfdbh@comcast.net>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C481F21F8BFE for <tsv-area@ietfa.amsl.com>; Tue, 12 Jul 2011 13:13:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.378
X-Spam-Level: 
X-Spam-Status: No, score=-102.378 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-pRSYN7VRh3 for <tsv-area@ietfa.amsl.com>; Tue, 12 Jul 2011 13:13:22 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0F321F8BF9 for <tsv-area@ietf.org>; Tue, 12 Jul 2011 13:13:22 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta13.westchester.pa.mail.comcast.net with comcast id 78Ce1h0060Fqzac5D8DPt0; Tue, 12 Jul 2011 20:13:23 +0000
Received: from davidPC ([67.189.235.106]) by omta08.westchester.pa.mail.comcast.net with comcast id 78DL1h01X2JQnJT3U8DNZ6; Tue, 12 Jul 2011 20:13:22 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <tsv-chairs@ietf.org>, <iesg@ietf.org>, <tsv-area@ietf.org>
Subject: DBH's AD Notes (my WGs plus DISCUSSES)
Date: Tue, 12 Jul 2011 16:13:08 -0400
Message-ID: <2C802824C09E48F39DEE6F373A71A8A9@davidPC>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_000A_01CC40AE.97EAB3D0"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcxA0B3AOjGOAGEXTKOrP5Rzhc7hlA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 20:13:23 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_000A_01CC40AE.97EAB3D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit



David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

------=_NextPart_000_000A_01CC40AE.97EAB3D0
Content-Type: text/plain;
	name="DBH's AD Notes 07-12-11.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="DBH's AD Notes 07-12-11.txt"

DBH's AD Notes
$Id:$
2011/07/12

This is what I perceive to be the current state of documents submitted =
to the AD/IESG for publication.
If you see anything missing, or anything incorrect, please contact me.

MISC NOTES

2011-07-13 (Wednesday): Draft Working Group agendas due by 17:00 PT =
(00:00 UTC), upload using IETF Meeting Materials Management Tool.=20
2011-07-15 (Friday): Early Bird registration and payment cut-off at =
17:00 PT (00:00 UTC).=20
2011-07-18 (Monday): Revised Working Group agendas due by 17:00 PT =
(00:00 UTC), upload using IETF Meeting Materials Management Tool.=20
2011-07-18 (Monday): Registration cancellation cut-off at 17:00 PT =
(00:00 UTC).=20
2011-07-22 (Friday): Final Pre-Registration and Pre-Payment cut-off at =
17:00 local meeting time.=20
2011-07-24 - 2011-07-29: 81st IETF Meeting in Quebec City, Canada.

MY WORKING GROUPS

ALTO
no submitted drafts

BEHAVE
- draft-ietf-behave-ftp64: Waiting for AD Go-Ahead

CDNI BOF
	WG approved

DECADE
- draft-ietf-decade-survey: IETF Last Call; IESG Telechat: 2011-08-11
- draft-ietf-decade-problem-statement: AD review: Revised ID need

FECFRAME
- draft-ietf-fecframe-raptor: AD Review - Revised ID needed
- draft-ietf-fecframe-rtp-raptor: AD Review=20
- draft-ietf-fecframe-config-signaling: AD Followup:Point Raised
	changes in -05- need shepherd approval and possibly WGLC to ensure =
consensus
- draft-ietf-fecframe-framework: RFC-Ed
- draft-ietf-fecframe-sdp-elements: RFC-Ed MISSREF (framework)
- draft-ietf-fecframe-dvb-al-fec: RFC-Ed MISREF (raptor and rtp-raptor)

NFSv4
no submitted drafts=20

PCN
- draft-ietf-pcn-sm-edge-behaviour-04: new ID; AD followup
- draft-ietf-pcn-cl-edge-behaviour: new ID; AD followup
	waiting for WG updates to standardize signaling protocol for cl and sm =
docs.

RMT
- draft-ietf-rmt-bb-fec-raptorq: RFC Ed Q
- draft-ietf-rmt-simple-auth-for-alc-norm-03 : new ID; AD followup (4 =
days)
- draft-ietf-rmt-flute-revised: AD Followup: Revised ID needed (7 days)

STORM
draft-ietf-storm-mpa-peer-connect: new ID; AD followup (28 days)

TCPM:

TSVWG
- recharter approved
- draft-ietf-tsvwg-rsvp-security-groupkeying: new ID; AD followup (18 =
days)
- draft-ietf-tsvwg-emergency-rsvp: MISREF (425 days)
	draft-ietf-intarea-router-alert-considerations in IESG Eval
- draft-ietf-tsvwg-iana-ports: EDIT IANA

OTHER DOCUMENTS

MY DISCUSSES (active -- something happened within last 30 days)

- draft-ietf-sipcore-event-rate-control: AD Followup=20
	new rev; same problems (1 day)
- draft-ietf-6man-flow-3697bis-06: in Last Call (ends 7-13) in =
discussion (1 day)
- draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat AD followup (19 =
days)
- draft- ietf-mpls-fastreroute-mib: AD Followup
	problems identified earlier still not addressed (0 days)
- draft-ietf-csi-dhcpv6-cga-ps: revised ID published; I need to =
re-review (44 days)


DISCUSSES (stalled -- I haven't heard anything from the authors or
document shepherd for 30-90 days)
- draft-ietf-savi-fcfs-09 Revised ID needed (47 days)
- draft-ietf-tcpm-persist: Rev ID needed; AD followup (33 days)

DISCUSSES (presumed dead -- I haven't heard anything from the authors
or document shepherd for over 90 days)
- draft-jabley-sink-arpa; Revised ID needed (200 days)=20





------=_NextPart_000_000A_01CC40AE.97EAB3D0--


From david.black@emc.com  Tue Jul 19 14:51:47 2011
Return-Path: <david.black@emc.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E61121F855B; Tue, 19 Jul 2011 14:51:47 -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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3VpV4FzduTV7; Tue, 19 Jul 2011 14:51:46 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7579021F8532; Tue, 19 Jul 2011 14:51:46 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6JLpcpF002562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jul 2011 17:51:38 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 19 Jul 2011 17:51:28 -0400
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6JLpROO018677; Tue, 19 Jul 2011 17:51:28 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Tue, 19 Jul 2011 17:51:27 -0400
From: <david.black@emc.com>
To: <c.raiciu@cs.ucl.ac.uk>
Date: Tue, 19 Jul 2011 17:51:25 -0400
Subject: RE: tsv-dir review of draft-ietf-mptcp-congestion-05
Thread-Topic: tsv-dir review of draft-ietf-mptcp-congestion-05
Thread-Index: AcxGMfH1yDA0GmMkRMaHlLDxny9PDQAK3j1w
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E058948B636@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05893924C1@MX14A.corp.emc.com> <7629FCE9-548E-404B-816D-7D04AD65D29D@cs.ucl.ac.uk>
In-Reply-To: <7629FCE9-548E-404B-816D-7D04AD65D29D@cs.ucl.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: ietf@ietf.org, multipathtcp@ietf.org, tsv-area@ietf.org, d.wischik@cs.ucl.ac.uk, tsv-dir@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 21:51:47 -0000

Costin,

The proposed -06 version sufficiently clarifies my one open issue.

I agree that the NSDI paper is an important citation and did not intend to
suggest that it be removed.  In addition, your decision to not cite RFC 312=
4
is ok with me.

Thank you for responding to the review.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------

> -----Original Message-----
> From: Costin Raiciu [mailto:c.raiciu@cs.ucl.ac.uk]
> Sent: Tuesday, July 19, 2011 12:35 PM
> To: Black, David
> Cc: tsv-dir; tsv-area; ietf; m.handley; d.wischik; multipathtcp
> Subject: Re: tsv-dir review of draft-ietf-mptcp-congestion-05
>=20
> Hi David,
>=20
> Thank you for your review.
>=20
> > Major:
> >
> > I have one open issue - the first two goals (in the Introduction) are t=
o have multipath
> > TCP connections behave somewhat like single-path connections in terms o=
f effects on
> > (fairness to) other traffic.  The algorithm specified accomplishes this=
 solely by
> > coupling the additive increase functionality across the flows, but allo=
wing each flow
> > to react to drops and congestion separately (no decrease coupling).  Th=
e draft does
> > not explain why increase coupling alone is sufficient to achieve these =
goals or what
> > compromise to the goals results from only coupling increases.
>=20
> Our proposal fully achieves goals 1 and 2 - fairness to single path tcp  =
and improve throughput. It
> does not fully achieve goal three - balancing congestion; fully achieving=
 goal 3 is very difficult,
> and an explanation is attempted in section 5; a reference is given to the=
 NSDI paper for further info.
>=20
> > Section 5 is a good start on this discussion, but it's not clear about =
what compromises
> > to the goals results from increase coupling only.  Section 5 criticizes=
 an alternative
> > that couples both increases and decreases for failing to achieve Goal 1=
, but doesn't
> > say what this approach achieves.  At most a few additional sentences in=
 Section 5 should
> > suffice to address this concern, and Section 2 should be edited to alig=
n with the
> > changes to Section 5.
>=20
> We have updated section 5 to make these points clear - they weren't clear=
 enough before.
>=20
> > Minor:
> >
> > While the [NSDI] paper is a fine place to reference work published in c=
onferences
> > and/or journals, RFC 3124 on the Congestion Manager is related IETF wor=
k and should
> > be cited here as an Informative Reference.
>=20
> The congestion manager is indeed related work and should be cited in a re=
search paper, but does not
> help understanding the congestion controller presented in this draft. We =
chose not to cite it
> explicitly.
>=20
> We chose to cite the NSDI paper because it describes in detail the design=
 choices that shaped the
> algorithm, and it will help an interested reader understand more about th=
e algorithm.
> The discussion section is itself a short high level summary of those deci=
sions.
>=20
> We attach the new version of this draft to this email (we cannot post a n=
ew version online of the
> draft because the IETF submission cutoff date has passed). Could you plea=
se check the draft and see if
> the issues you raised have been clarified?
>=20
> We will post the draft as soon as submissions reopen after the IETF
>=20
> Thanks,
> Costin

From guyingjie@huawei.com  Wed Jul 20 04:26:12 2011
Return-Path: <guyingjie@huawei.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E17C21F8640 for <tsv-area@ietfa.amsl.com>; Wed, 20 Jul 2011 04:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.34
X-Spam-Level: 
X-Spam-Status: No, score=-100.34 tagged_above=-999 required=5 tests=[AWL=-1.795, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_GRNTEE=2.3, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NJ7f2LkeSZXZ for <tsv-area@ietfa.amsl.com>; Wed, 20 Jul 2011 04:26:11 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3F41E21F85F5 for <tsv-area@ietf.org>; Wed, 20 Jul 2011 04:26:11 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOM00NL5QFK3Y@szxga05-in.huawei.com> for tsv-area@ietf.org; Wed, 20 Jul 2011 19:26:09 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOM005RJQFG6S@szxga05-in.huawei.com> for tsv-area@ietf.org; Wed, 20 Jul 2011 19:26:08 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml206-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACK28448; Wed, 20 Jul 2011 19:26:08 +0800 (CST)
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 20 Jul 2011 19:26:03 +0800
Received: from SZXEML511-MBS.china.huawei.com ([169.254.4.170]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0270.001; Wed, 20 Jul 2011 19:26:07 +0800
Date: Wed, 20 Jul 2011 11:26:05 +0000
From: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
Subject: A late annoucement on TSV-Area relavant drafts
X-Originating-IP: [172.24.2.41]
To: "tsv-area@ietf.org" <tsv-area@ietf.org>
Message-id: <A27496C192613C44A82D819E1B98DB570F62431A@SZXEML511-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_ZMBzIcvW+VtC8x9K5F1afQ)"
Content-language: zh-CN
Accept-Language: zh-CN, en-US
Thread-topic: A late annoucement on TSV-Area relavant drafts
Thread-index: AcxGzYVr/3Wt0OE1T76LlKhTW0z09A==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 11:26:12 -0000

--Boundary_(ID_ZMBzIcvW+VtC8x9K5F1afQ)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: base64

SGkgYWxsLA0KDQpXZSBzdWJtaXRlZCBhIGRyYWZ0IHRvIGRlc2NyaWJlIGEgcHJvYmxlbSB0aGF0
IGlzIHJlbGF0ZWQgdG8gb3BlcmF0aW9uYWwgc3RhdGUgbWlncmF0aW9uIGluIGRhdGEgY2VudGVy
Lg0KDQpUaGUgZHJhZnQgaXMgb3JpZ2luYWxseSBwb3N0ZWQgdG8gT1BTQVdHLCBidXQgd2UgYWxz
byB0aGluayBpdCdzIHJlbGF0ZWQgdG8gVFNWLUFyZWEgYXMgd2VsbC4gU28gd2Ugd291bGQgbGlr
ZSB0byBpbnZpdGUgcGVvcGxlIGluIFRTVi1BcmVhIHRvIGRpc2N1c3MgdGhlIHByb2JsZW0uDQoN
ClRoZSBVUkwgb2YgdGhlIGRyYWZ0IGlzDQoNCmh0dHA6Ly90b29scy5pZXRmLm9yZy9pZC9kcmFm
dC1ndS1vcHNhd2ctcG9saWNpZXMtbWlncmF0aW9uLTAwLnR4dA0KDQpWTShWaXJ0dWFsIE1hY2hp
bmUpIG1pZ3JhdGlvbiBpcyB2ZXJ5IHBvcHVsYXIgbm93LiBWaXJ0dWFsaXphdGlvbiBhbmQgVmly
dHVhbCBNYWNoaW5lIChWTSkgbWlncmF0aW9uIHByb3ZpZGUgRGF0YSBDZW50ZXIgd2l0aCBmZWFz
aWJpbGl0eSBhbmQgaW1wcm92ZXMgdGhlIHV0aWxpemF0aW9uIG9mIGxpbWl0ZWQgcGh5c2ljYWwg
cmVzb3VyY2UsIGUuZy4gc3dpdGNoZXMvcm91dGVycywgc2VydmVycyBhbmQgbGlua3MuICBNZWFu
d2hpbGUsIGEgdmFyaWV0eSBvZiBwb2xpY2llcyAoZS5nLiAgQUNMLCBmaXJld2FsbHMsIGxvYWQg
YmFsYW5jZXJzLCBJUFMgYW5kIFFvUykgYXJlIGRlcGxveWVkIGluIERhdGEgQ2VudGVyIHRvIGlt
cHJvdmUgc3lzdGVtIHNlY3VyaXR5IGFuZCBndXJhbnRlZSBTTEEuICBUaG9zZSBwb2xpY2VzIGFy
ZSBleGVjdXRlZCBieSBydWxlcyBjb25maWd1cmVkIG9yIGdlbmVyYXRlZCBvbiBuZXR3b3JrIGRl
dmljZXMuICBFLmcuIHBhY2tldCBmaWx0ZXJpbmcgcG9saWNpZXMgYXJlIGV4ZWN1dGVkIGJ5IEFj
Y2VzcyBDb250cm9sIExpc3Qgb24gc3dpdGNoZXMgb3IgZmlyZXdhbGxzLiAgQW5vdGhlciBleGFt
cGxlIGlzIExvYWQgYmFsYW5jZXIgKExCKSB3aG8gZXh0YWJsaXNoZXMgVENQL0hUVFAgY29ubmVj
dGlvbnMgd2l0aCBleHRlcm5hbCBjbGllbnRzIGFuZCBiYWxhbmNlcyBjb25uZWN0aW9ucyBhbW9u
ZyBzZXJ2ZXIgZmFybS4gRHVyaW5nIHRoaXMgcHJvY2VzcywgVENQIHN0YXRlIHRhYmxlcyBhcmUg
ZHluYW1pY2FsbHkgZ2VuZXJhdGVkIG9uIExCLiAgV2hlbiBWTSBtaWdyYXRlcywgdGhlIG5ldHdv
cmsgZGV2aWNlcyB0aGF0IHByb2Nlc3NpbmcgYW5kIGZvcndhcmQgVk0ncyBwYWNrZXRzIG1heSBj
aGFuZ2UuICBJbiBvcmRlciB0byBrZWVwIFZNJ3MgcnVubmluZyBzZXJpdmVzIGFuZCBndWFucmFu
dGVlIHNlY3VyaXR5IG9uIG5ldyBwbGFjZSwgVk0tcmVsZXZhbnQgc3RhdGVzLCBpbmNsdWRpbmcg
Y29uZmlndXJhdGlvbiBzdGF0ZSAoc3RhdGljIHBvbGljaWVzKSBhcyB3ZWxsIGFzIHRoZSBvcGVy
YXRpb25hbCBzdGF0ZSAoZHluYW1pY2FsbHkgZ2VuZXJhdGVkIGluZm9ybWF0aW9uKSwgbmVlZCB0
byBtaWdyYXRlIHdpdGggVk0uDQoNCg0KDQpJbiBvcmRlciB0byBtYWtlIGRlZXAgcmVzZWFyY2gg
aW4gdGhpcyBwcm9ibGVtLCB3ZSBjb21wb3NlIGEgc29sdXRpb24gc3VydmV5IGRyYWZ0IGFuZCBh
IGdhcCBhbmFseXNpcyBkcmFmdCwgeW91IGNhbiBnZXQgdGhlbSBmcm9tDQoNCmh0dHA6Ly90b29s
cy5pZXRmLm9yZy9pZC9kcmFmdC1ndS1vcHNhd2ctcG9saWNpZXMtbWlncmF0aW9uLXNvbHV0aW9u
LXN1cnZleS0wMC50eHQNCg0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2lkL2RyYWZ0LXdhbmctb3Bz
YXdnLXBvbGljaWVzLW1pZ3JhdGlvbi1nYXAtYW5hbHlzaXMtMDAudHh0DQoNCg0KDQpXaGVuIHdl
IHdyb3RlIGRvd24gdGhlIHNvbHV0aW9uIHN1cnZleSBkcmFmdCwgd2UgcmVhbGl6ZWQgdGhhdCBw
YXJ0IG9mIHRoZSBzb2x1dGlvbiBtYXkgYmUgYXBwcm9wcmlhdGUgaW4gVFNWLUFyZWEuDQoNCg0K
DQogV2UgaGF2ZSByYWlzZWQgc29tZSBkaXNjdXNzaW9uIGluIE9QU0FXRywgYW5kIGdldCBzdXBw
b3J0cyBmcm9tIHNldmVyYWwgcGVyc29ucy4gSWYgeW91IGFyZSBpbnRlcmVzdGVkIGluIGxlYXJu
aW5nIHRoZSBkaXNjdXNzaW9uLCBwbGVhc2UgZ28gdGhlcmUgYW5kIGZpbmQgdGhlIHRocmVhZHMg
dGhhdCBpbmNsdWRlICdwb2xpY2llcyBtaWdyYXRpb24nIG9yICdkcmFmdC1ndS1vcHNhd2ctcG9s
aWNpZXMtbWlncmF0aW9uJyBpbiB0aGUgdGl0bGVzLg0KDQoNCg0KQW55IGNvbW1lbnRzIGZyb20g
eW91IGFyZSBoaWdobHkgYXBwcmVjaWF0ZWQuIEFuZCB3ZSBob3BlIHRvIGdldCBhIHRpbWUgc2xv
dCBpbiBJRVRGIDgxIG1lZXRpbmcgdG8gZGlzY3VzcyB0aGUgVFNWIHJlbGF0ZWQgcGFydCBpbiBU
U1YtQXJlYSBzZXNzaW9uLg0KDQoNCg0KVGhhbmsgeW91IHZlcnkgbXVjaC4NCg0KDQoNCg0K

--Boundary_(ID_ZMBzIcvW+VtC8x9K5F1afQ)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<style id="owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p>Hi all,</p>
<p>We submited a draft to describe a problem that is related to operational state migration in data center.</p>
<p>The draft is originally posted to OPSAWG, but we also think it's related to TSV-Area as well. So we would like to invite people in TSV-Area to discuss the problem.
</p>
<p>The URL of the draft is </p>
<p><a href="http://tools.ietf.org/id/draft-gu-opsawg-policies-migration-00.txt">http://tools.ietf.org/id/draft-gu-opsawg-policies-migration-00.txt</a></p>
<p>VM(Virtual Machine) migration is very popular now. Virtualization and Virtual Machine (VM) migration provide Data Center&nbsp;with feasibility and improves the utilization of limited physical&nbsp;resource, e.g. switches/routers, servers and links.&nbsp; Meanwhile, a&nbsp;variety
 of policies (e.g.&nbsp; ACL, firewalls, load balancers, IPS and&nbsp;QoS) are deployed in Data Center to improve system security and&nbsp;gurantee SLA.&nbsp; Those polices are executed by rules configured or&nbsp;generated on network devices.&nbsp; E.g. packet filtering policies are&nbsp;executed
 by Access Control List on switches or firewalls.&nbsp; Another&nbsp;example is Load balancer (LB) who extablishes TCP/HTTP connections&nbsp;with external clients and balances connections among server farm.&nbsp;During this process, TCP state tables are dynamically generated&nbsp;on
 LB.&nbsp; When VM migrates, the network devices that processing and&nbsp;forward VM's packets may change.&nbsp; In order to keep VM's running serives and guanrantee security on new place, VM-relevant states,&nbsp;including configuration state (static policies) as well as the&nbsp;operational
 state&nbsp;(dynamically generated information), need to migrate with VM. </p>
<p>&nbsp;</p>
<p>In order to make deep research in this problem, we compose a solution survey draft and a gap analysis draft, you can get&nbsp;them from
</p>
<p><a href="http://tools.ietf.org/id/draft-gu-opsawg-policies-migration-solution-survey-00.txt">http://tools.ietf.org/id/draft-gu-opsawg-policies-migration-solution-survey-00.txt</a></p>
<p><a href="http://tools.ietf.org/id/draft-wang-opsawg-policies-migration-gap-analysis-00.txt">http://tools.ietf.org/id/draft-wang-opsawg-policies-migration-gap-analysis-00.txt</a></p>
<p>&nbsp;</p>
<p>When we wrote down the solution survey draft, we realized that part of the solution may be&nbsp;appropriate in&nbsp;TSV-Area.
</p>
<p>&nbsp;</p>
<p>&nbsp;We have raised some discussion in OPSAWG, and get supports from several persons. If you are interested in learning the discussion, please go there and find the threads that include 'policies migration' or 'draft-gu-opsawg-policies-migration' in the titles.
</p>
<p>&nbsp;</p>
<p>Any comments from you are highly appreciated. And we hope to get a time slot in IETF 81 meeting to discuss the TSV related part in TSV-Area session.</p>
<p>&nbsp;</p>
<p>Thank you very much.</p>
<p>&nbsp;</p>
<p><br>
&nbsp;</p>
</div>
</body>
</html>

--Boundary_(ID_ZMBzIcvW+VtC8x9K5F1afQ)--

From david.black@emc.com  Fri Jul 22 08:20:10 2011
Return-Path: <david.black@emc.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D4221F8B04; Fri, 22 Jul 2011 08:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sqBHNO4DpATr; Fri, 22 Jul 2011 08:20:07 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 69E8921F8AFB; Fri, 22 Jul 2011 08:20:07 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6MFJuJ4014340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Jul 2011 11:19:57 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 22 Jul 2011 11:19:47 -0400
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p6MFJkMv029113; Fri, 22 Jul 2011 11:19:46 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Fri, 22 Jul 2011 11:19:45 -0400
From: <david.black@emc.com>
To: <wangdanhua@huawei.com>, <opsawg@ietf.org>, <tsvwg@ietf.org>, <tsv-area@ietf.org>
Date: Fri, 22 Jul 2011 11:19:45 -0400
Subject: RE: Looking forward to your comments: Survey and Gap Analysis for Policies	and Dynamic Information Migration in Data Center
Thread-Topic: Looking forward to your comments: Survey and Gap Analysis for Policies	and Dynamic Information Migration in Data Center
Thread-Index: AcwvxII6NIOr4KEqT7e/9oY69KijZAAA/D3AAGJst3ABYAr98ARo4rlA
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E058948BC34@MX14A.corp.emc.com>
References: <AFD688AF30E249418739DBDC55B9C75B271BA4@SZXEML504-MBX.china.huawei.com>
In-Reply-To: <AFD688AF30E249418739DBDC55B9C75B271BA4@SZXEML504-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7C4DFCE962635144B8FAE8CA11D0BF1E058948BC34MX14Acorpemcc_"
MIME-Version: 1.0
X-EMM-MHVC: 1
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 15:20:10 -0000

--_000_7C4DFCE962635144B8FAE8CA11D0BF1E058948BC34MX14Acorpemcc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The draft-gu-opsa-policies-migration-00 is not completely clear to me.  The=
 network diagrams, starting with Figure 1, do not indicate the L2 vs. L3 ne=
twork boundaries (e.g., what's the scope of the VLANs mentioned in Section =
3.1), and the function of the "Gateway" at the top of the diagrams is not d=
escribed.  This is a concern, as if there's no L2 connectivity through the =
Gateway across the two sides of the diagram, the left-to-right VM migration=
 use case shown in Figure 1 can be problematic, because all of the VM's L2 =
connectivity breaks (e.g., ARP cache entries contain unreachable L2 address=
es).  Section 3.2 refers to a "proxy" - what is it and where is it in the n=
etwork diagrams?

That said, I believe that the ACL and related firewall state transfer probl=
ems exist, but I'm concerned that other problems (e.g., DHCP state) may be =
artifacts of unclear assumptions about network architecture that may not be=
 reasonable.  For DHCP in particular, a few well-placed DHCP proxies may so=
lve the problem, but the network diagrams are sufficiently unclear that I c=
an't figure out where to locate the proxies.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of w=
angdanhua
Sent: Wednesday, June 29, 2011 11:05 PM
To: opsawg@ietf.org; tsvwg@ietf.org; dispatch@ietf.org
Subject: Looking forward to your comments: Survey and Gap Analysis for Poli=
cies and Dynamic Information Migration in Data Center

Hi all,

A few days ago, we sent a draft considering "policies and dynamic informati=
on migration in DC" to OPSAWG, the draft ID is "draft-gu-opsa-policies-migr=
ation-00" and its URL is http://datatracker.ietf.org/doc/draft-gu-opsa-poli=
cies-migration/ . Based on this problem statement draft as well as the disc=
ussion at the 80th IETF conference, we also performed a gap analysis betwee=
n dynamic information migration (DIM) requirements and the most related IET=
F works. We sent a gap analysis draft to the OPSAWG, here is the URL  http:=
//datatracker.ietf.org/doc/draft-wang-opsawg-policies-migration-gap-analysi=
s/ . Following is the abstract of this draft. We sincerely hope that you wo=
uld give your valuable comment or options if you are interest in this draft=
.

With the virtualization of Data Center, the number of VM explodes. VM can p=
lay different roles in Data Center, such as end-host, server, firewall, and=
 so on. Also, VM can be migrated to any places within Data Center, even to =
another Data Center. Since running services shouldn't be significantly inte=
rrupted while VM migrates, VM related policies and dynamic information gene=
rated by any devices must be transferred to destination devices during a pr=
oper short period. [I.D-gu-opsa-policies-migration-00] has introduced more =
detail problem statement and corresponding considerations. We wish we could=
 benefit from existing work to realize accurate dynamic information migrati=
on (DIM).  Therefore, we engaged in the investigation of related IETF works=
 right after general requirements of DIM are defined.  Since the solution f=
or DIM has not been decided yet, and the author can envision several kinds =
of solution, e.g. centralized or distributed.  It's unrealistic to enumerat=
e all the related works for an uncertain solution.  So, in this draft, only=
 the most related IETF work, MIDCOM protocol, has been evaluated to find ou=
t whether it can fully support DIM or which characteristics can be reused i=
n DIM. The author would like analyze other related IETF works when the WG m=
ake further decision on DIM solution.

Following a short description of general DIM requirements, this draft prese=
nts a brief survey of MIDCOM protocol, and then lists the gap between MIDCO=
M and DIM requirements.  The final section presents possible working scope =
on the topic of DIM in IETF.


Best Regards
Danhua Wang
HuaWei Technology Co. Ltd.
Nanjing, China

--_000_7C4DFCE962635144B8FAE8CA11D0BF1E058948BC34MX14Acorpemcc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple style=3D'text-justify-trim:punctuation'><div class=3DWordSectio=
n1><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courie=
r New";color:black'>The draft-gu-opsa-policies-migration-00 is not complete=
ly clear to me.&nbsp; The network diagrams, starting with Figure 1, do not =
indicate the L2 vs. L3 network boundaries (e.g., what&#8217;s the scope of =
the VLANs mentioned in Section 3.1), and the function of the &#8220;Gateway=
&#8221; at the top of the diagrams is not described.&nbsp; This is a concer=
n, as if there&#8217;s no L2 connectivity through the Gateway across the tw=
o sides of the diagram, the left-to-right VM migration use case shown in Fi=
gure 1 can be problematic, because all of the VM&#8217;s L2 connectivity br=
eaks (e.g., ARP cache entries contain unreachable L2 addresses).&nbsp; Sect=
ion 3.2 refers to a &#8220;proxy&#8221; &#8211; what is it and where is it =
in the network diagrams?<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:"Courier New";color:black'>That said, I believe that the ACL and rela=
ted firewall state transfer problems exist, but I&#8217;m concerned that ot=
her problems (e.g., DHCP state) may be artifacts of unclear assumptions abo=
ut network architecture that may not be reasonable.&nbsp; For DHCP in parti=
cular, a few well-placed DHCP proxies may solve the problem, but the networ=
k diagrams are sufficiently unclear that I can&#8217;t figure out where to =
locate the proxies.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:=
p></span></p><div><p class=3DMsoNormal align=3Dleft style=3D'text-align:lef=
t'><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>T=
hanks,<br>--David<br>----------------------------------------------------<b=
r>David L. Black, Distinguished Engineer<br>EMC Corporation, 176 South St.,=
 Hopkinton, MA&nbsp; 01748<br>+1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAX: +1 (508) 293-7786<br>davi=
d.black@emc.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: +1 (978) =
394-7754<br>----------------------------------------------------</span><spa=
n style=3D'font-size:11.0pt;font-family:"Courier New";color:black'><o:p></o=
:p></span></p></div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><div style=
=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><di=
v><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in'><p class=3DMsoNormal align=3Dleft style=3D'text-align:left'><b><=
span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</sp=
an></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] <b>On Behalf Of </b>=
wangdanhua<br><b>Sent:</b> Wednesday, June 29, 2011 11:05 PM<br><b>To:</b> =
opsawg@ietf.org; tsvwg@ietf.org; dispatch@ietf.org<br><b>Subject:</b> Looki=
ng forward to your comments: Survey and Gap Analysis for Policies and Dynam=
ic Information Migration in Data Center<o:p></o:p></span></p></div></div><p=
 class=3DMsoNormal align=3Dleft style=3D'text-align:left'><o:p>&nbsp;</o:p>=
</p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Times=
 New Roman","serif"'>Hi all,<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal style=3D'line-height:14.4pt;backgr=
ound:white'><span style=3D'font-size:10.0pt;font-family:"Times New Roman","=
serif"'>A few days ago, we sent a draft considering &#8220;policies and dyn=
amic information migration in DC&#8221; to OPSAWG, the draft ID is &#8220;d=
raft-gu-opsa-policies-migration-00&#8221; and its URL is<span style=3D'colo=
r:#1F497D'> </span><a href=3D"http://datatracker.ietf.org/doc/draft-gu-opsa=
-policies-migration/">http://datatracker.ietf.org/doc/draft-gu-opsa-policie=
s-migration/</a> . Based on this problem statement draft as well as the dis=
cussion at the 80th IETF conference, we also performed a gap analysis betwe=
en dynamic information migration (DIM) requirements and the most related IE=
TF works. We sent a gap analysis draft to the OPSAWG, here is the <span sty=
le=3D'color:#1F497D'>URL </span>&nbsp;<a href=3D"http://datatracker.ietf.or=
g/doc/draft-wang-opsawg-policies-migration-gap-analysis/">http://datatracke=
r.ietf.org/doc/draft-wang-opsawg-policies-migration-gap-analysis/</a> . Fol=
lowing is the abstract of this draft. We sincerely hope that you would give=
 your valuable comment or options if you are interest in this draft.<o:p></=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fa=
mily:"Times New Roman","serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal style=3D'text-autospace:none'><span style=3D'font-size:10.0pt;font-fa=
mily:"Times New Roman","serif"'>With the virtualization of Data Center, the=
 number of VM explodes. VM can play different roles in Data Center, such as=
 end-host, server, firewall, and so on. Also, VM can be migrated to any pla=
ces within Data Center, even to another Data Center. Since running services=
 shouldn't be significantly interrupted while VM migrates, VM related polic=
ies and dynamic information generated by any devices must be transferred to=
 destination devices during a proper short period. [I.D-gu-opsa-policies-mi=
gration-00] has introduced more detail problem statement and corresponding =
considerations. We wish we could benefit from existing work to realize accu=
rate dynamic information migration (DIM).&nbsp; Therefore, we engaged in th=
e investigation of related IETF works right after general requirements of D=
IM are defined.&nbsp; Since the solution for DIM has not been decided yet, =
and the author can envision several kinds of solution, e.g. centralized or =
distributed.&nbsp; It's unrealistic to enumerate all the related works for =
an uncertain solution.&nbsp; So, in this draft, only the most related IETF =
work, MIDCOM protocol, has been evaluated to find out whether it can fully =
support DIM or which characteristics can be reused in DIM. The author would=
 like analyze other related IETF works when the WG make further decision on=
 DIM solution.<o:p></o:p></span></p><p class=3DMsoNormal style=3D'text-auto=
space:none'><span style=3D'font-size:10.0pt;font-family:"Times New Roman","=
serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal style=3D'text-auto=
space:none'><span style=3D'font-size:10.0pt;font-family:"Times New Roman","=
serif"'>Following a short description of general DIM requirements, this dra=
ft presents a brief survey of MIDCOM protocol, and then lists the gap betwe=
en MIDCOM and DIM requirements.&nbsp; The final section presents possible w=
orking scope on the topic of DIM in IETF.<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;font-family:"Times New Roman","ser=
if"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:10.0pt;font-family:"Times New Roman","serif"'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Times =
New Roman","serif"'>Best Regards<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>Danh=
ua Wang<span style=3D'color:#1F497D'><o:p></o:p></span></span></p><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>HuaWei Technology Co. Ltd.<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>Nanjing,=
 China<o:p></o:p></span></p></div></div></body></html>=

--_000_7C4DFCE962635144B8FAE8CA11D0BF1E058948BC34MX14Acorpemcc_--

From guyingjie@huawei.com  Fri Jul 22 10:10:31 2011
Return-Path: <guyingjie@huawei.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 110F621F8B03; Fri, 22 Jul 2011 10:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.757
X-Spam-Level: 
X-Spam-Status: No, score=-99.757 tagged_above=-999 required=5 tests=[AWL=-2.207, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fLagPqYUreqh; Fri, 22 Jul 2011 10:10:30 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 8D75A21F8B01; Fri, 22 Jul 2011 10:10:29 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOQ005FRVPGYF@szxga04-in.huawei.com>; Sat, 23 Jul 2011 01:10:28 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOQ00DJ3VPGJM@szxga04-in.huawei.com>; Sat, 23 Jul 2011 01:10:28 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml203-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACN49557; Sat, 23 Jul 2011 01:10:27 +0800 (CST)
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sat, 23 Jul 2011 01:10:19 +0800
Received: from SZXEML511-MBS.china.huawei.com ([169.254.4.170]) by szxeml409-hub.china.huawei.com ([169.254.89.141]) with mapi id 14.01.0270.001; Sat, 23 Jul 2011 01:10:23 +0800
Date: Fri, 22 Jul 2011 17:10:22 +0000
From: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
Subject: =?gb2312?B?tPC4tDogTG9va2luZyBmb3J3YXJkIHRvIHlvdXIgY29tbWVudHM6IFN1cnZl?= =?gb2312?B?eSBhbmQgR2FwIEFuYWx5c2lzIGZvciBQb2xpY2llcyBhbmQgRHluYW1pYyBJ?= =?gb2312?Q?nformation_Migration_in_Data_Center?=
X-Originating-IP: [172.24.2.41]
To: "david.black@emc.com" <david.black@emc.com>, wangdanhua <wangdanhua@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Message-id: <A27496C192613C44A82D819E1B98DB570F62476A@SZXEML511-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_ztVK390Ub98kst6MJscTHg)"
Content-language: zh-CN
Accept-Language: zh-CN, en-US
Thread-topic: Looking forward to your comments: Survey and Gap Analysis for Policies and Dynamic Information Migration in Data Center
Thread-index: AQHMSI09YA3711ENs0+eDCA+BlQhRQ==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 17:10:31 -0000

--Boundary_(ID_ztVK390Ub98kst6MJscTHg)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: base64

SGkgRGF2aWQsDQoNClRoYW5rIHlvdSBmb3IgdGhlIGNvbW1lbnRzLg0KDQpJIHJlbW92ZWQgVFNW
V0cgZnJvbSB0aGUgbGlzdCwgYmVjYXVzZSBJIHRhbGtlZCB3aXRoIFRTVldHIGNoYWlycyBhbmQg
dGhleSByZWdhcmRzIHRoYXQgdGhpcyB0b3BpYyBub3QgcmVsYXRlZCB0byBUU1ZXRy4NCg0KSSBh
Z3JlZSB0aGF0IHRoZSBkaWFncmFtIGRvZXNuJ3Qgc2hvdyB0aGUgTDIgY29ubmVjdGl2aXRpZXMg
YmV0d2VlbiB0d28gRGF0YSBDZW50ZXJzLiBJbiBvcmRlciB0byBtYWtlIHRoZSBWTSBtaWdyYXRp
b24gc3VjY2Vzc2Z1bCBiZXR3ZWVuIERDcywgTDIgQ29ubmVjdGl2aXRpZXMgYXJlIG5lY2Vzc2Fy
eS4NCg0KQ3VycmVudGx5LCBtb3N0IFZNIG1pZ3JhdGlvbiBpcyB3aXRoaW4gb25lIERDIHRvIGd1
YXJhbnRlZSBMMiBjb25uZWN0aXZpdHkuIEhvd2V2ZXIsICBJJ3ZlIGhlYXJkIGZyb20gbWFueSBj
dXN0b21lcnMgdGhhdCB0aGV5IG5lZWQgdG8gbWlncmF0ZSBWTXMgYW1vbmcgRGF0YSBDZW50ZXJz
IGZvciBzZXZlcmFsIHJlYXNvbnMsIGUuZy4gZGlzYXN0ZXIgYXZvaWRhbmNlLCByZXNvdXJjZSBj
b25zb2xpZGF0aW9uLCBhbmQgdHJhZmZpYyBvcHRpbWl6YXRpb24uICBUbyBlbmFibGUgdGhpcywg
c2V2ZXJhbCB0ZWNobm9sb2dpZXMgYXJlIHN1Z2dlc3RlZCwgZS5nLiBFb01QTFMsIFZQTFMgYW5k
IFR1bm5lbGxpbmcuIFNvbWUgSUVURiB3b3JrIG1heSBhbHNvIGJlIGhlbHBmdWwgdG8gcmVzb2x2
ZSB0aGlzIHByb2JsZW0sIGUuZy4gTElTUC4NCg0KSSBkaWRuJ3QgZHJhdyB0aGUgTDIgY29ubmVj
dGl2aXRpZXMgYmV0d2VlbiBEQ3MsIGJlY2F1c2UgSSBoYXZlbid0IGZpZ3VyZSBvdXQgYSBzdWl0
YWJsZSB3YXkgdG8gc2hvdyBtYW55IHBvc3NpYmxlIGtpbmRzIG9mIEwyIGNvbm5lY3Rpdml0aWVz
LiAgSSB3aWxsIGZpZ3VyZSBvdXQgaW4gdGhlIG5leHQgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoN
ClRoZSBwcm94eSBtZWFucyBQcm94eSBGaXJld2FsbCB3aGljaCBjYW4gZXN0YWJsaXNoIGNvbm5l
Y3Rpb25zIHdpdGggZXh0ZXJuYWwgY2xpZW50cyBmb3IgbG9jYWwgc2VydmVycy4NCg0KDQoNClRo
ZSBhcmNoaXRlY3R1cmUgaW4gdGhpcyBkcmFmdCBpcyBxdWl0ZSBzaW1wbGUsIHdoaWxlIHRoZSBh
cmNoaXRlY3R1cmUgaW4gcmVhbCBEQyBjb3VsZCBiZSB2YXJpb3VzIGFuZCBjb21wbGljYXRlZC4g
SSB3b3VsZCBpbnZpdGUgbW9yZSBPcGVyYXRvcnMgYW5kIFZlbmRvcnMgdG8gaGVscCB0byBpbXBy
b3ZlIHRoZSBhcmNoaXRlY3R1cmUgcGFydC4NCg0KDQoNCllvdXIgY29tbWVudHMgYXJlIHZlcnkg
aGVscGZ1bC4NCg0KQ291bGQgeW91IGdpdmUgbW9yZSBjb21tZW50cyBvbiBTdG9yYWdlIE1pZ3Jh
dGlvbj8NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0Kt6K8/sjLOiB0c3Yt
YXJlYS1ib3VuY2VzQGlldGYub3JnIFt0c3YtYXJlYS1ib3VuY2VzQGlldGYub3JnXSC0+rHtIGRh
dmlkLmJsYWNrQGVtYy5jb20gW2RhdmlkLmJsYWNrQGVtYy5jb21dDQq3osvNyrG85DogMjAxMcTq
N9TCMjLI1SAyMzoxOQ0Ktb06IHdhbmdkYW5odWE7IG9wc2F3Z0BpZXRmLm9yZzsgdHN2d2dAaWV0
Zi5vcmc7IHRzdi1hcmVhQGlldGYub3JnDQrW98ziOiBSRTogTG9va2luZyBmb3J3YXJkIHRvIHlv
dXIgY29tbWVudHM6IFN1cnZleSBhbmQgR2FwIEFuYWx5c2lzIGZvciBQb2xpY2llcyBhbmQgRHlu
YW1pYyBJbmZvcm1hdGlvbiBNaWdyYXRpb24gaW4gRGF0YSBDZW50ZXINCg0KVGhlIGRyYWZ0LWd1
LW9wc2EtcG9saWNpZXMtbWlncmF0aW9uLTAwIGlzIG5vdCBjb21wbGV0ZWx5IGNsZWFyIHRvIG1l
LiAgVGhlIG5ldHdvcmsgZGlhZ3JhbXMsIHN0YXJ0aW5nIHdpdGggRmlndXJlIDEsIGRvIG5vdCBp
bmRpY2F0ZSB0aGUgTDIgdnMuIEwzIG5ldHdvcmsgYm91bmRhcmllcyAoZS5nLiwgd2hhdKGvcyB0
aGUgc2NvcGUgb2YgdGhlIFZMQU5zIG1lbnRpb25lZCBpbiBTZWN0aW9uIDMuMSksIGFuZCB0aGUg
ZnVuY3Rpb24gb2YgdGhlIKGwR2F0ZXdheaGxIGF0IHRoZSB0b3Agb2YgdGhlIGRpYWdyYW1zIGlz
IG5vdCBkZXNjcmliZWQuICBUaGlzIGlzIGEgY29uY2VybiwgYXMgaWYgdGhlcmWhr3Mgbm8gTDIg
Y29ubmVjdGl2aXR5IHRocm91Z2ggdGhlIEdhdGV3YXkgYWNyb3NzIHRoZSB0d28gc2lkZXMgb2Yg
dGhlIGRpYWdyYW0sIHRoZSBsZWZ0LXRvLXJpZ2h0IFZNIG1pZ3JhdGlvbiB1c2UgY2FzZSBzaG93
biBpbiBGaWd1cmUgMSBjYW4gYmUgcHJvYmxlbWF0aWMsIGJlY2F1c2UgYWxsIG9mIHRoZSBWTaGv
cyBMMiBjb25uZWN0aXZpdHkgYnJlYWtzIChlLmcuLCBBUlAgY2FjaGUgZW50cmllcyBjb250YWlu
IHVucmVhY2hhYmxlIEwyIGFkZHJlc3NlcykuICBTZWN0aW9uIDMuMiByZWZlcnMgdG8gYSChsHBy
b3h5obEgqEMgd2hhdCBpcyBpdCBhbmQgd2hlcmUgaXMgaXQgaW4gdGhlIG5ldHdvcmsgZGlhZ3Jh
bXM/DQoNClRoYXQgc2FpZCwgSSBiZWxpZXZlIHRoYXQgdGhlIEFDTCBhbmQgcmVsYXRlZCBmaXJl
d2FsbCBzdGF0ZSB0cmFuc2ZlciBwcm9ibGVtcyBleGlzdCwgYnV0IEmhr20gY29uY2VybmVkIHRo
YXQgb3RoZXIgcHJvYmxlbXMgKGUuZy4sIERIQ1Agc3RhdGUpIG1heSBiZSBhcnRpZmFjdHMgb2Yg
dW5jbGVhciBhc3N1bXB0aW9ucyBhYm91dCBuZXR3b3JrIGFyY2hpdGVjdHVyZSB0aGF0IG1heSBu
b3QgYmUgcmVhc29uYWJsZS4gIEZvciBESENQIGluIHBhcnRpY3VsYXIsIGEgZmV3IHdlbGwtcGxh
Y2VkIERIQ1AgcHJveGllcyBtYXkgc29sdmUgdGhlIHByb2JsZW0sIGJ1dCB0aGUgbmV0d29yayBk
aWFncmFtcyBhcmUgc3VmZmljaWVudGx5IHVuY2xlYXIgdGhhdCBJIGNhbqGvdCBmaWd1cmUgb3V0
IHdoZXJlIHRvIGxvY2F0ZSB0aGUgcHJveGllcy4NCg0KVGhhbmtzLA0KLS1EYXZpZA0KLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KRGF2aWQgTC4g
QmxhY2ssIERpc3Rpbmd1aXNoZWQgRW5naW5lZXINCkVNQyBDb3Jwb3JhdGlvbiwgMTc2IFNvdXRo
IFN0LiwgSG9wa2ludG9uLCBNQSAgMDE3NDgNCisxICg1MDgpIDI5My03OTUzICAgICAgICAgICAg
IEZBWDogKzEgKDUwOCkgMjkzLTc3ODYNCmRhdmlkLmJsYWNrQGVtYy5jb20gICAgICAgIE1vYmls
ZTogKzEgKDk3OCkgMzk0LTc3NTQNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCg0KRnJvbTogdHN2d2ctYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRv
OnRzdndnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiB3YW5nZGFuaHVhDQpTZW50OiBX
ZWRuZXNkYXksIEp1bmUgMjksIDIwMTEgMTE6MDUgUE0NClRvOiBvcHNhd2dAaWV0Zi5vcmc7IHRz
dndnQGlldGYub3JnOyBkaXNwYXRjaEBpZXRmLm9yZw0KU3ViamVjdDogTG9va2luZyBmb3J3YXJk
IHRvIHlvdXIgY29tbWVudHM6IFN1cnZleSBhbmQgR2FwIEFuYWx5c2lzIGZvciBQb2xpY2llcyBh
bmQgRHluYW1pYyBJbmZvcm1hdGlvbiBNaWdyYXRpb24gaW4gRGF0YSBDZW50ZXINCg0KSGkgYWxs
LA0KDQpBIGZldyBkYXlzIGFnbywgd2Ugc2VudCBhIGRyYWZ0IGNvbnNpZGVyaW5nIKGwcG9saWNp
ZXMgYW5kIGR5bmFtaWMgaW5mb3JtYXRpb24gbWlncmF0aW9uIGluIERDobEgdG8gT1BTQVdHLCB0
aGUgZHJhZnQgSUQgaXMgobBkcmFmdC1ndS1vcHNhLXBvbGljaWVzLW1pZ3JhdGlvbi0wMKGxIGFu
ZCBpdHMgVVJMIGlzIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtZ3Utb3Bz
YS1wb2xpY2llcy1taWdyYXRpb24vIC4gQmFzZWQgb24gdGhpcyBwcm9ibGVtIHN0YXRlbWVudCBk
cmFmdCBhcyB3ZWxsIGFzIHRoZSBkaXNjdXNzaW9uIGF0IHRoZSA4MHRoIElFVEYgY29uZmVyZW5j
ZSwgd2UgYWxzbyBwZXJmb3JtZWQgYSBnYXAgYW5hbHlzaXMgYmV0d2VlbiBkeW5hbWljIGluZm9y
bWF0aW9uIG1pZ3JhdGlvbiAoRElNKSByZXF1aXJlbWVudHMgYW5kIHRoZSBtb3N0IHJlbGF0ZWQg
SUVURiB3b3Jrcy4gV2Ugc2VudCBhIGdhcCBhbmFseXNpcyBkcmFmdCB0byB0aGUgT1BTQVdHLCBo
ZXJlIGlzIHRoZSBVUkwgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtd2Fu
Zy1vcHNhd2ctcG9saWNpZXMtbWlncmF0aW9uLWdhcC1hbmFseXNpcy8gLiBGb2xsb3dpbmcgaXMg
dGhlIGFic3RyYWN0IG9mIHRoaXMgZHJhZnQuIFdlIHNpbmNlcmVseSBob3BlIHRoYXQgeW91IHdv
dWxkIGdpdmUgeW91ciB2YWx1YWJsZSBjb21tZW50IG9yIG9wdGlvbnMgaWYgeW91IGFyZSBpbnRl
cmVzdCBpbiB0aGlzIGRyYWZ0Lg0KDQpXaXRoIHRoZSB2aXJ0dWFsaXphdGlvbiBvZiBEYXRhIENl
bnRlciwgdGhlIG51bWJlciBvZiBWTSBleHBsb2Rlcy4gVk0gY2FuIHBsYXkgZGlmZmVyZW50IHJv
bGVzIGluIERhdGEgQ2VudGVyLCBzdWNoIGFzIGVuZC1ob3N0LCBzZXJ2ZXIsIGZpcmV3YWxsLCBh
bmQgc28gb24uIEFsc28sIFZNIGNhbiBiZSBtaWdyYXRlZCB0byBhbnkgcGxhY2VzIHdpdGhpbiBE
YXRhIENlbnRlciwgZXZlbiB0byBhbm90aGVyIERhdGEgQ2VudGVyLiBTaW5jZSBydW5uaW5nIHNl
cnZpY2VzIHNob3VsZG4ndCBiZSBzaWduaWZpY2FudGx5IGludGVycnVwdGVkIHdoaWxlIFZNIG1p
Z3JhdGVzLCBWTSByZWxhdGVkIHBvbGljaWVzIGFuZCBkeW5hbWljIGluZm9ybWF0aW9uIGdlbmVy
YXRlZCBieSBhbnkgZGV2aWNlcyBtdXN0IGJlIHRyYW5zZmVycmVkIHRvIGRlc3RpbmF0aW9uIGRl
dmljZXMgZHVyaW5nIGEgcHJvcGVyIHNob3J0IHBlcmlvZC4gW0kuRC1ndS1vcHNhLXBvbGljaWVz
LW1pZ3JhdGlvbi0wMF0gaGFzIGludHJvZHVjZWQgbW9yZSBkZXRhaWwgcHJvYmxlbSBzdGF0ZW1l
bnQgYW5kIGNvcnJlc3BvbmRpbmcgY29uc2lkZXJhdGlvbnMuIFdlIHdpc2ggd2UgY291bGQgYmVu
ZWZpdCBmcm9tIGV4aXN0aW5nIHdvcmsgdG8gcmVhbGl6ZSBhY2N1cmF0ZSBkeW5hbWljIGluZm9y
bWF0aW9uIG1pZ3JhdGlvbiAoRElNKS4gIFRoZXJlZm9yZSwgd2UgZW5nYWdlZCBpbiB0aGUgaW52
ZXN0aWdhdGlvbiBvZiByZWxhdGVkIElFVEYgd29ya3MgcmlnaHQgYWZ0ZXIgZ2VuZXJhbCByZXF1
aXJlbWVudHMgb2YgRElNIGFyZSBkZWZpbmVkLiAgU2luY2UgdGhlIHNvbHV0aW9uIGZvciBESU0g
aGFzIG5vdCBiZWVuIGRlY2lkZWQgeWV0LCBhbmQgdGhlIGF1dGhvciBjYW4gZW52aXNpb24gc2V2
ZXJhbCBraW5kcyBvZiBzb2x1dGlvbiwgZS5nLiBjZW50cmFsaXplZCBvciBkaXN0cmlidXRlZC4g
IEl0J3MgdW5yZWFsaXN0aWMgdG8gZW51bWVyYXRlIGFsbCB0aGUgcmVsYXRlZCB3b3JrcyBmb3Ig
YW4gdW5jZXJ0YWluIHNvbHV0aW9uLiAgU28sIGluIHRoaXMgZHJhZnQsIG9ubHkgdGhlIG1vc3Qg
cmVsYXRlZCBJRVRGIHdvcmssIE1JRENPTSBwcm90b2NvbCwgaGFzIGJlZW4gZXZhbHVhdGVkIHRv
IGZpbmQgb3V0IHdoZXRoZXIgaXQgY2FuIGZ1bGx5IHN1cHBvcnQgRElNIG9yIHdoaWNoIGNoYXJh
Y3RlcmlzdGljcyBjYW4gYmUgcmV1c2VkIGluIERJTS4gVGhlIGF1dGhvciB3b3VsZCBsaWtlIGFu
YWx5emUgb3RoZXIgcmVsYXRlZCBJRVRGIHdvcmtzIHdoZW4gdGhlIFdHIG1ha2UgZnVydGhlciBk
ZWNpc2lvbiBvbiBESU0gc29sdXRpb24uDQoNCkZvbGxvd2luZyBhIHNob3J0IGRlc2NyaXB0aW9u
IG9mIGdlbmVyYWwgRElNIHJlcXVpcmVtZW50cywgdGhpcyBkcmFmdCBwcmVzZW50cyBhIGJyaWVm
IHN1cnZleSBvZiBNSURDT00gcHJvdG9jb2wsIGFuZCB0aGVuIGxpc3RzIHRoZSBnYXAgYmV0d2Vl
biBNSURDT00gYW5kIERJTSByZXF1aXJlbWVudHMuICBUaGUgZmluYWwgc2VjdGlvbiBwcmVzZW50
cyBwb3NzaWJsZSB3b3JraW5nIHNjb3BlIG9uIHRoZSB0b3BpYyBvZiBESU0gaW4gSUVURi4NCg0K
DQpCZXN0IFJlZ2FyZHMNCkRhbmh1YSBXYW5nDQpIdWFXZWkgVGVjaG5vbG9neSBDby4gTHRkLg0K
TmFuamluZywgQ2hpbmENCg==

--Boundary_(ID_ztVK390Ub98kst6MJscTHg)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<style>@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page WordSection1 {margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-ser=
if"; FONT-SIZE: 10.5pt
}
LI.MsoNormal {
	TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-ser=
if"; FONT-SIZE: 10.5pt
}
DIV.MsoNormal {
	TEXT-ALIGN: justify; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-ser=
if"; FONT-SIZE: 10.5pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext
}
SPAN.EmailStyle18 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d
}
SPAN.EmailStyle19 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d
}
SPAN.EmailStyle20 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d
}
SPAN.EmailStyle21 {
	FONT-STYLE: normal; FONT-FAMILY: "Courier New"; COLOR: black; FONT-WEIGHT:=
 normal; TEXT-DECORATION: none
}
.MsoChpDefault {
	FONT-SIZE: 10pt
}
</style><style id=3D"owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body lang=3D"EN-US" vlink=3D"purple" link=3D"blue" fPStyle=3D"1" ocsi=3D"0=
">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">
<p>Hi David,</p>
<p>Thank you for the comments.</p>
<p>I removed TSVWG from the list, because I talked with TSVWG chairs and th=
ey regards that this topic not related to TSVWG.</p>
<p>I agree that the diagram doesn't show the L2 connectivities between two =
Data Centers. In order to make the VM migration successful between DCs, L2 =
Connectivities&nbsp;are necessary.&nbsp;</p>
<p>Currently, most&nbsp;VM migration is within one DC to guarantee L2 conne=
ctivity.&nbsp;However, &nbsp;I've heard from&nbsp;many customers that they&=
nbsp;need to migrate VMs among Data Centers for several reasons, e.g. disas=
ter avoidance, resource consolidation, and&nbsp;traffic optimization.&nbsp;
 To enable this, several technologies are suggested, e.g. EoMPLS, VPLS and =
Tunnelling. Some IETF work&nbsp;may&nbsp;also be helpful to resolve this pr=
oblem, e.g. LISP.</p>
<p>I didn't draw the L2 connectivities between DCs, because I haven't figur=
e out a suitable way to show many possible kinds of&nbsp;L2 connectivities.=
&nbsp; I will figure out in the next version of the draft.
</p>
<p>The proxy means Proxy Firewall which can establish connections with exte=
rnal clients for local servers.
</p>
<p>&nbsp;</p>
<p>The architecture in this draft&nbsp;is quite simple, while the architect=
ure in real DC could be various and complicated. I would invite more Operat=
ors and Vendors to help to improve the architecture part.</p>
<p>&nbsp;</p>
<p>Your comments are very helpful. </p>
<p>Could you give more comments on Storage Migration? </p>
<hr tabindex=3D"-1">
<p></p>
<div style=3D"FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px=
">
<div style=3D"DIRECTION: ltr" id=3D"divRpF401554"><font color=3D"#000000" s=
ize=3D"2" face=3D"Tahoma"><b>=B7=A2=BC=FE=C8=CB:</b> tsv-area-bounces@ietf.=
org [tsv-area-bounces@ietf.org] =B4=FA=B1=ED david.black@emc.com [david.bla=
ck@emc.com]<br>
<b>=B7=A2=CB=CD=CA=B1=BC=E4:</b> 2011=C4=EA7=D4=C222=C8=D5 23:19<br>
<b>=B5=BD:</b> wangdanhua; opsawg@ietf.org; tsvwg@ietf.org; tsv-area@ietf.o=
rg<br>
<b>=D6=F7=CC=E2:</b> RE: Looking forward to your comments: Survey and Gap A=
nalysis for Policies and Dynamic Information Migration in Data Center<br>
</font><br>
</div>
<div></div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">The draft-gu-opsa-policies-migration-00 is not comple=
tely clear to me.&nbsp; The network diagrams, starting with Figure 1, do no=
t indicate the L2 vs. L3 network boundaries
 (e.g., what=A1=AFs the scope of the VLANs mentioned in Section 3.1), and t=
he function of the =A1=B0Gateway=A1=B1 at the top of the diagrams is not de=
scribed.&nbsp; This is a concern, as if there=A1=AFs no L2 connectivity thr=
ough the Gateway across the two sides of the diagram, the
 left-to-right VM migration use case shown in Figure 1 can be problematic, =
because all of the VM=A1=AFs L2 connectivity breaks (e.g., ARP cache entrie=
s contain unreachable L2 addresses).&nbsp; Section 3.2 refers to a =A1=B0pr=
oxy=A1=B1 =A8C what is it and where is it in the network
 diagrams?</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt">That said, I believe that the ACL and related firewal=
l state transfer problems exist, but I=A1=AFm concerned that other problems=
 (e.g., DHCP state) may be artifacts of unclear
 assumptions about network architecture that may not be reasonable.&nbsp; F=
or DHCP in particular, a few well-placed DHCP proxies may solve the problem=
, but the network diagrams are sufficiently unclear that I can=A1=AFt figur=
e out where to locate the proxies.</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<div>
<p style=3D"TEXT-ALIGN: left" class=3D"MsoNormal" align=3D"left"><span styl=
e=3D"FONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: 10pt">Thanks,<br>
--David<br>
----------------------------------------------------<br>
David L. Black, Distinguished Engineer<br>
EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748<br>
&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; FAX: &#43;1 (508) 293-7786<br>
david.black@emc.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: &#43;=
1 (978) 394-7754<br>
----------------------------------------------------</span><span style=3D"F=
ONT-FAMILY: 'Courier New'; COLOR: black; FONT-SIZE: 11pt"></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Courier New'; COLOR: bl=
ack; FONT-SIZE: 10pt"></span>&nbsp;</p>
<div style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; PA=
DDING-BOTTOM: 0in; PADDING-LEFT: 4pt; PADDING-RIGHT: 0in; BORDER-TOP: mediu=
m none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">
<div>
<div style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING=
-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1p=
t solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p style=3D"TEXT-ALIGN: left" class=3D"MsoNormal" align=3D"left"><b><span s=
tyle=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</span></=
b><span style=3D"FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> tsvw=
g-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]
<b>On Behalf Of </b>wangdanhua<br>
<b>Sent:</b> Wednesday, June 29, 2011 11:05 PM<br>
<b>To:</b> opsawg@ietf.org; tsvwg@ietf.org; dispatch@ietf.org<br>
<b>Subject:</b> Looking forward to your comments: Survey and Gap Analysis f=
or Policies and Dynamic Information Migration in Data Center</span></p>
</div>
</div>
<p style=3D"TEXT-ALIGN: left" class=3D"MsoNormal" align=3D"left">&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Times New Roman','serif=
'; FONT-SIZE: 10pt">Hi all,</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Times New Roman','serif=
'; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt; BACKGROUND: white" class=3D"MsoNormal"><sp=
an style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 10pt">A few =
days ago, we sent a draft considering =A1=B0policies and dynamic informatio=
n migration in DC=A1=B1 to OPSAWG, the draft ID
 is =A1=B0draft-gu-opsa-policies-migration-00=A1=B1 and its URL is<span sty=
le=3D"COLOR: #1f497d">
</span><a href=3D"http://datatracker.ietf.org/doc/draft-gu-opsa-policies-mi=
gration/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-gu-opsa-p=
olicies-migration/</a> . Based on this problem statement draft as well as t=
he discussion at the 80th IETF conference,
 we also performed a gap analysis between dynamic information migration (DI=
M) requirements and the most related IETF works. We sent a gap analysis dra=
ft to the OPSAWG, here is the
<span style=3D"COLOR: #1f497d">URL </span>&nbsp;<a href=3D"http://datatrack=
er.ietf.org/doc/draft-wang-opsawg-policies-migration-gap-analysis/" target=
=3D"_blank">http://datatracker.ietf.org/doc/draft-wang-opsawg-policies-migr=
ation-gap-analysis/</a> . Following is the abstract
 of this draft. We sincerely hope that you would give your valuable comment=
 or options if you are interest in this draft.</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Times New Roman','serif=
'; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p style=3D"TEXT-AUTOSPACE: " class=3D"MsoNormal"><span style=3D"FONT-FAMIL=
Y: 'Times New Roman','serif'; FONT-SIZE: 10pt">With the virtualization of D=
ata Center, the number of VM explodes. VM can play different roles in Data =
Center, such as end-host, server, firewall,
 and so on. Also, VM can be migrated to any places within Data Center, even=
 to another Data Center. Since running services shouldn't be significantly =
interrupted while VM migrates, VM related policies and dynamic information =
generated by any devices must be
 transferred to destination devices during a proper short period. [I.D-gu-o=
psa-policies-migration-00] has introduced more detail problem statement and=
 corresponding considerations. We wish we could benefit from existing work =
to realize accurate dynamic information
 migration (DIM).&nbsp; Therefore, we engaged in the investigation of relat=
ed IETF works right after general requirements of DIM are defined.&nbsp; Si=
nce the solution for DIM has not been decided yet, and the author can envis=
ion several kinds of solution, e.g. centralized
 or distributed.&nbsp; It's unrealistic to enumerate all the related works =
for an uncertain solution.&nbsp; So, in this draft, only the most related I=
ETF work, MIDCOM protocol, has been evaluated to find out whether it can fu=
lly support DIM or which characteristics can
 be reused in DIM. The author would like analyze other related IETF works w=
hen the WG make further decision on DIM solution.</span></p>
<p style=3D"TEXT-AUTOSPACE: " class=3D"MsoNormal"><span style=3D"FONT-FAMIL=
Y: 'Times New Roman','serif'; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p style=3D"TEXT-AUTOSPACE: " class=3D"MsoNormal"><span style=3D"FONT-FAMIL=
Y: 'Times New Roman','serif'; FONT-SIZE: 10pt">Following a short descriptio=
n of general DIM requirements, this draft presents a brief survey of MIDCOM=
 protocol, and then lists the gap between
 MIDCOM and DIM requirements.&nbsp; The final section presents possible wor=
king scope on the topic of DIM in IETF.</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Times New Roman','serif=
'; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Times New Roman','serif=
'; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Times New Roman','serif=
'; FONT-SIZE: 10pt">Best Regards</span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY: 'Times New Roman','serif=
'; FONT-SIZE: 10pt">Danhua Wang<span style=3D"COLOR: #1f497d"></span></span=
></p>
<p class=3D"MsoNormal"><span style=3D"COLOR: #1f497d">HuaWei Technology Co.=
 Ltd.</span></p>
<p class=3D"MsoNormal"><span style=3D"COLOR: #1f497d">Nanjing, China</span>=
</p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--Boundary_(ID_ztVK390Ub98kst6MJscTHg)--

From ietfdbh@comcast.net  Mon Jul 25 05:05:00 2011
Return-Path: <ietfdbh@comcast.net>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B487E21F84CA for <tsv-area@ietfa.amsl.com>; Mon, 25 Jul 2011 05:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.813
X-Spam-Level: 
X-Spam-Status: No, score=-101.813 tagged_above=-999 required=5 tests=[AWL=0.786, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4drQS8WOxBf0 for <tsv-area@ietfa.amsl.com>; Mon, 25 Jul 2011 05:05:00 -0700 (PDT)
Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by ietfa.amsl.com (Postfix) with ESMTP id 0588321F8AEA for <tsv-area@ietf.org>; Mon, 25 Jul 2011 04:59:54 -0700 (PDT)
Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta08.emeryville.ca.mail.comcast.net with comcast id CBuD1h0011wfjNsA8BzqKl; Mon, 25 Jul 2011 11:59:50 +0000
Received: from davidPC ([130.129.19.147]) by omta23.emeryville.ca.mail.comcast.net with comcast id CBzU1h00J3APkkq8jBzXbM; Mon, 25 Jul 2011 11:59:40 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <tsv-area@ietf.org>, <tsv-chairs@ietf.org>
Subject: TSV AD Office Hours
Date: Mon, 25 Jul 2011 07:59:36 -0400
Message-ID: <F09BCD3B27624AB4BE0659FB364152FC@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
Thread-Index: AcxKwlLZfKLViCjfSBmLjNhLKFlD9Q==
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 12:05:00 -0000

Hi,

13:00 - 15:00 TSV AD Office Hours 
Room 304B

Feel free to drop by.
Please notify us in advance of topics you want to discuss, and the
time you think you'll need.

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)


From ietfdbh@comcast.net  Mon Jul 25 09:11:23 2011
Return-Path: <ietfdbh@comcast.net>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3586F11E80BA for <tsv-area@ietfa.amsl.com>; Mon, 25 Jul 2011 09:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.128
X-Spam-Level: 
X-Spam-Status: No, score=-102.128 tagged_above=-999 required=5 tests=[AWL=0.471, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEb+HeL6tCSv for <tsv-area@ietfa.amsl.com>; Mon, 25 Jul 2011 09:11:22 -0700 (PDT)
Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by ietfa.amsl.com (Postfix) with ESMTP id 7639E21F8C3E for <tsv-area@ietf.org>; Mon, 25 Jul 2011 07:35:12 -0700 (PDT)
Received: from omta24.emeryville.ca.mail.comcast.net ([76.96.30.92]) by qmta05.emeryville.ca.mail.comcast.net with comcast id CCvU1h0031zF43QA5Eb9XQ; Mon, 25 Jul 2011 14:35:09 +0000
Received: from davidPC ([130.129.19.147]) by omta24.emeryville.ca.mail.comcast.net with comcast id CEaG1h00C3APkkq8kEaKH9; Mon, 25 Jul 2011 14:34:29 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Songhaibin'" <haibin.song@huawei.com>, <tsv-area@ietf.org>, <tsv-chairs@ietf.org>
References: <F09BCD3B27624AB4BE0659FB364152FC@davidPC> <E33E01DFD5BEA24B9F3F18671078951FB45737@szxeml524-mbs.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951FB45737@szxeml524-mbs.china.huawei.com>
Subject: RE: TSV AD Office Hours
Date: Mon, 25 Jul 2011 10:34:55 -0400
Message-ID: <09B1E58579B24C698480C7989FF1743C@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
Thread-Index: AcxKwlLZfKLViCjfSBmLjNhLKFlD9QACit4sAALcbZA=
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 16:11:23 -0000

whoops. 

Thursday 
> 13:00 - 15:00 TSV AD Office Hours
> Room 304B
> 
> Feel free to drop by.
> Please notify us in advance of topics you want to discuss, and the
> time you think you'll need.
> 
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
> 
> 


From guyingjie@huawei.com  Mon Jul 25 12:51:17 2011
Return-Path: <guyingjie@huawei.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3097F11E80AF; Mon, 25 Jul 2011 12:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.08
X-Spam-Level: 
X-Spam-Status: No, score=-102.08 tagged_above=-999 required=5 tests=[AWL=0.316, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nlOlvICyGf20; Mon, 25 Jul 2011 12:51:16 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 8565411E80A8; Mon, 25 Jul 2011 12:51:16 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOW001J6N5F7G@szxga04-in.huawei.com>; Tue, 26 Jul 2011 03:51:15 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOW005CJN5FS2@szxga04-in.huawei.com>; Tue, 26 Jul 2011 03:51:15 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml207-edg.china.huawei.com) ([172.24.2.119])	by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACU84232; Tue, 26 Jul 2011 03:51:15 +0800 (CST)
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 26 Jul 2011 03:51:12 +0800
Received: from SZXEML511-MBS.china.huawei.com ([169.254.4.170]) by szxeml409-hub.china.huawei.com ([169.254.89.141]) with mapi id 14.01.0270.001; Tue, 26 Jul 2011 03:51:14 +0800
Date: Mon, 25 Jul 2011 19:51:13 +0000
From: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
Subject: Re: TSV AD Office Hours
In-reply-to: <09B1E58579B24C698480C7989FF1743C@davidPC>
X-Originating-IP: [172.24.2.41]
To: David Harrington <ietfdbh@comcast.net>, Songhaibin <haibin.song@huawei.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>,  "tsv-chairs@ietf.org" <tsv-chairs@ietf.org>
Message-id: <A27496C192613C44A82D819E1B98DB570F624E4E@SZXEML511-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: TSV AD Office Hours
Thread-index: AcxKwlLZfKLViCjfSBmLjNhLKFlD9QACit4sAALcbZAACwBKgA==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <F09BCD3B27624AB4BE0659FB364152FC@davidPC> <E33E01DFD5BEA24B9F3F18671078951FB45737@szxeml524-mbs.china.huawei.com> <09B1E58579B24C698480C7989FF1743C@davidPC>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 19:51:17 -0000

SGkgRGF2aWQgYW5kIFdlc2xleSwNCkkgd291bGQgbGlrZSB0byBoYXZlIGEgdGFsayBvbiBwb2xp
Y2llcyBtaWdyYXRpb24uIA0KSSB3aWxsIG5lZWQgYWJvdXQgaGFsZiBhbiBob3VyLiANClRoYW5r
cy4gDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQq3orz+yMs6IHRz
di1hcmVhLWJvdW5jZXNAaWV0Zi5vcmcgW3Rzdi1hcmVhLWJvdW5jZXNAaWV0Zi5vcmddILT6se0g
RGF2aWQgSGFycmluZ3RvbiBbaWV0ZmRiaEBjb21jYXN0Lm5ldF0NCreiy83KsbzkOiAyMDExxOo3
1MIyNcjVIDIyOjM0DQq1vTogU29uZ2hhaWJpbjsgdHN2LWFyZWFAaWV0Zi5vcmc7IHRzdi1jaGFp
cnNAaWV0Zi5vcmcNCtb3zOI6IFJFOiBUU1YgQUQgT2ZmaWNlIEhvdXJzDQoNCndob29wcy4NCg0K
VGh1cnNkYXkNCj4gMTM6MDAgLSAxNTowMCBUU1YgQUQgT2ZmaWNlIEhvdXJzDQo+IFJvb20gMzA0
Qg0KPg0KPiBGZWVsIGZyZWUgdG8gZHJvcCBieS4NCj4gUGxlYXNlIG5vdGlmeSB1cyBpbiBhZHZh
bmNlIG9mIHRvcGljcyB5b3Ugd2FudCB0byBkaXNjdXNzLCBhbmQgdGhlDQo+IHRpbWUgeW91IHRo
aW5rIHlvdSdsbCBuZWVkLg0KPg0KPiBEYXZpZCBIYXJyaW5ndG9uDQo+IERpcmVjdG9yLCBJRVRG
IFRyYW5zcG9ydCBBcmVhDQo+IGlldGZkYmhAY29tY2FzdC5uZXQgKHByZWZlcnJlZCBmb3IgaWV0
ZikNCj4gZGJoYXJyaW5ndG9uQGh1YXdlaXN5bWFudGVjLmNvbQ0KPiArMSA2MDMgODI4IDE0MDEg
KGNlbGwpDQo+DQo+

From guyingjie@huawei.com  Mon Jul 25 15:12:48 2011
Return-Path: <guyingjie@huawei.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BEB121F8BDB for <tsv-area@ietfa.amsl.com>; Mon, 25 Jul 2011 15:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.195
X-Spam-Level: 
X-Spam-Status: No, score=-104.195 tagged_above=-999 required=5 tests=[AWL=2.403, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koL2ocm9i2rS for <tsv-area@ietfa.amsl.com>; Mon, 25 Jul 2011 15:12:47 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 64C3621F8B9E for <tsv-area@ietf.org>; Mon, 25 Jul 2011 15:12:47 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOW00LOBTP9QH@szxga03-in.huawei.com> for tsv-area@ietf.org; Tue, 26 Jul 2011 06:12:45 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOW007OFTP9AB@szxga03-in.huawei.com> for tsv-area@ietf.org; Tue, 26 Jul 2011 06:12:45 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml205-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACP01592; Tue, 26 Jul 2011 06:12:45 +0800 (CST)
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 26 Jul 2011 06:12:42 +0800
Received: from SZXEML511-MBS.china.huawei.com ([169.254.4.170]) by szxeml410-hub.china.huawei.com ([169.254.101.122]) with mapi id 14.01.0270.001; Tue, 26 Jul 2011 06:12:45 +0800
Date: Mon, 25 Jul 2011 22:12:43 +0000
From: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
Subject: Some introduction and explanation to Policies Migration. .
X-Originating-IP: [172.24.2.41]
To: "tsv-area@ietf.org" <tsv-area@ietf.org>
Message-id: <A27496C192613C44A82D819E1B98DB570F624EDE@SZXEML511-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_+ozsB2wjuUMCusClaciszA)"
Content-language: zh-CN
Accept-Language: zh-CN, en-US
Thread-topic: Some introduction and explanation to Policies Migration. .
Thread-index: AcxLFTyrckK78P5pQVSMY0hBiTX+9g==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 22:12:48 -0000

--Boundary_(ID_+ozsB2wjuUMCusClaciszA)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi all,

Hope you can have a look at the not-too-long email so that it could be easier for you to understand Thursday's presentation.

Thanks in advance.



In fact the name should be changed to "Operational State Migration" which can reflect the real problem.



In Data Center, Virtual Machine migrates from old location to new location for many reasons. In addition to migration of virtual resouces on server (solutions are provided by VM Vendors like VMWare), the network states also need to migrate, if we wang to keep running services undisrupted during VM Hot/Live Migration.

Take Tcp states on Firewall as an example. During VM running TCP states keep changing. If the VM migrates without the TCP states on Firewall migrate to the new Firewall, existing connections will be broken.



Two kinds of states on network: Configure state(configured by Network Manager) and operational state(generated by network devices based on traffic).  We focus on operational state migration, which is very time-sensitive, but the solution may also be applicable for configuration state migration.



Currently, I was suggested to look at MIDCOM and PCP to find out whether they can be reused. We have made gap analysis with MIDCOM. First of all, I need to point out that MIDCOM/PCP/new protocol for transfering the state is only part of the solution. The whole solution also need to consider two essential parts, i.e. 'Time trigger' and 'Feedback to VM Manager'.



Thank you for your attention. Any comments are highly appreciated.



B.R.

Yingjie Gu

--Boundary_(ID_+ozsB2wjuUMCusClaciszA)
Content-type: text/html; charset=gb2312
Content-transfer-encoding: 7BIT

<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<style id="owaParaStyle">P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p>Hi all,</p>
<p>Hope you can have a look at the not-too-long email so that it could be easier for you to understand Thursday's presentation.</p>
<p>Thanks in advance. </p>
<p>&nbsp;</p>
<p>In fact the name should be changed to &quot;Operational State Migration&quot; which can reflect the real problem.</p>
<p>&nbsp;</p>
<p>In Data Center, Virtual Machine migrates from old location to new location for many reasons. In addition to migration of virtual resouces on server (solutions are provided by VM Vendors like VMWare), the network states also need to migrate, if we wang to
 keep running services undisrupted during VM Hot/Live Migration. </p>
<p>Take Tcp states on Firewall as an example. During VM running TCP states keep changing. If the VM migrates&nbsp;without the TCP states on Firewall migrate to the new Firewall, existing connections will be broken.
</p>
<p>&nbsp;</p>
<p>Two kinds of states on network: Configure state(configured by Network Manager) and operational state(generated by network devices based on traffic).&nbsp;&nbsp;We focus on operational&nbsp;state migration, which is very time-sensitive, but the solution may also be applicable
 for&nbsp;configuration state migration. &nbsp; </p>
<p>&nbsp;</p>
<p>Currently, I was suggested to look at MIDCOM&nbsp;and PCP to find out whether they can be reused. We have made gap analysis with MIDCOM. First of all, I need to point out that MIDCOM/PCP/new protocol for transfering the state is only part of the solution. The
 whole solution also need to consider two essential parts, i.e. 'Time trigger' and 'Feedback to VM Manager'.
</p>
<p>&nbsp;</p>
<p>Thank you for your attention. Any comments are highly appreciated.</p>
<p>&nbsp;</p>
<p>B.R.</p>
<p>Yingjie Gu</p>
</div>
</body>
</html>

--Boundary_(ID_+ozsB2wjuUMCusClaciszA)--

From bittau@gmail.com  Wed Jul 27 11:44:31 2011
Return-Path: <bittau@gmail.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9486B11E8143; Wed, 27 Jul 2011 11:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wcTEgjSeKmbt; Wed, 27 Jul 2011 11:44:30 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5715611E813F; Wed, 27 Jul 2011 11:44:30 -0700 (PDT)
Received: by gwb20 with SMTP id 20so1543665gwb.31 for <multiple recipients>; Wed, 27 Jul 2011 11:44:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-echelon:user-agent; bh=HDs6k0Bpd0mqByBrGrQ5vH1S5Q1d0svGWm/yyEKUeyU=; b=J6fNgk2Xg74GnrbRLZ+4hOmf0BXGsEhFYQNeyjIvzM40I4S+6RhA9a8+wEz5n6YbC6 BDYnF+GHFZ3x8KVP9Du1BuppB2Dh3hAYYEa0sOe2iI7jvlhWaI2fucI7/YNYor2k9PKp 8Tif4WvCajJJqL8mJ6RVjvWqqyNAyQ6N/ucyA=
Received: by 10.142.248.34 with SMTP id v34mr92493wfh.107.1311792269305; Wed, 27 Jul 2011 11:44:29 -0700 (PDT)
Received: from tapir.cs.ucl.ac.uk (sorbo.scs.stanford.edu [171.66.3.100]) by mx.google.com with ESMTPS id k3sm136397pbj.29.2011.07.27.11.44.27 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Jul 2011 11:44:27 -0700 (PDT)
Sender: Andrea Bittau <bittau@gmail.com>
Received: by tapir.cs.ucl.ac.uk (Postfix, from userid 0) id D0B1E4810172; Wed, 27 Jul 2011 11:42:58 -0700 (PDT)
Date: Wed, 27 Jul 2011 11:42:57 -0700
From: Andrea Bittau <bittau@cs.stanford.edu>
To: David McGrew <mcgrew@cisco.com>
Subject: Re: [saag] fyi: tcpcrypt draft
Message-ID: <20110727184256.GA3690@shorty>
References: <4DC6C56D.6040709@ieca.com> <D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cisco.com>
X-Echelon: Bush Bomb War KGB
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Wed, 27 Jul 2011 12:31:56 -0700
Cc: tcpcrypt@scs.stanford.edu, Sean Turner <turners@ieca.com>, tsv-area@ietf.org, saag@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2011 18:48:57 -0000

Sorry for the late reply!  Comments inline.

On Tue, May 10, 2011 at 04:03:58PM -0700, David McGrew wrote:
> Hello Tcpcrypt authors,
> 
> I have skimmed the internet draft and the USENIX Security paper on
> tcpcrypt, and while it is interesting and thought-provoking work, I
> have a hard time understanding what the goals of the I-D are
> relative to the TCP standard.  The draft says "Standards Track";
> would Experimental be more appropriate?  It mentions the following
> objectives:

We don't have a strong opinion about a standard's track vs.
experimental categorization, so experimental is fine.  We'll be happy to
reevaluate in the future.

> "Tcpcrypt maintains the confidentiality of data transmitted in TCP
> segments against a passive eavesdropper.  It can be used to protect
> already established TCP connections against denial-of-service
> attacks involving injection of forged RST segments or
> desynchronizing of sequence numbers."  Yes, but TLS and IPsec
> perform the former function, and IPsec and TCP-AO perform the
> latter.  In addition, running TCP over DTLS would also accomplishes
> the latter function; this practice is done in some (so-called)
> SSLVPNs.

Yes, tcpcrypt immediately offers confidentiality of data against a
passive eavesdropper, which is better than the status quo, but this is
not our ideal situation.  Our ideal situation is to provide strong
secrecy and integrity protected by mutual authentication of the two
endpoints.  The benefit of tcpcrypt is that it immediately provides this
protection against passive eavesdroppers, while also making it as easy
and efficient as possible to achieve the stronger security when
applications can make use of appropriate authentication credentials.

While IPSec is capable of providing opportunistic encryption, it does
not do so "immediately".  In particular, plenty of machines run
operating systems that support IPSec, yet do not use IPSec for security.
Tcpcrypt, by contrast, is designed to be "on by default." It therefore
has to require less configuration and provide better interoperability
than IPSec with middleboxes such as NATs.  IPSec, because it is at the
network layer, is also harder to integrate with application-level
notions of authentication, which are typically tied to a particular TCP
connection rather than a pair of machines.  (E.g., it is reasonable to
run two different browsers on the same client, and use those two
browsers to log into the same web site with two different accounts.)

TLS is closer to tcpcrypt.  It could also be used for opportunistic
encryption.  However, compared to tcpcrypt, TLS still requires more
configuration, is not compatible with all TCP applications, and has a
heavier impact on server performance.  All of these factors make it
harder to enable TLS by default.  The combination of TLS and TCP-AO (the
latter requiring setting up a pre-shared key between endpoints) would be
harder still to make on by default.  Finally, the fact that TLS does not
always provide forward secrecy is a disadvantage compared to tcpcrypt.

Being a single, integrated, zero-configuration (once kernels support it)
solution that can be incrementally deployed puts tcpcrypt at an
advantage compared to other solutions that need to be used in tandem for
more complete security, each coming with their own configuration
requirements.

> "Finally, applications that perform authentication can obtain
> end-to-end confidentiality and integrity guarantees by tying
> authentication to tcpcrypt Session ID values."  This seems like a
> potentially useful feature, though it seems similar to channel
> binding (RFCs 5056 and 5929).

Yes it's the same concept and we implemented in tcpcrypt's core to allow
briding to app-level authentication.  We also use the same mechanism to
name sessions for session caching.

> "Tcpcrypt is designed to require relatively low overhead,
> particularly at servers, so as to be useful even in the case of
> servers accepting many TCP connections per second."  The idea of
> batching signatures seems like a useful contribution that could be
> put to good use by servers that are under heavy loads.  But why not
> implement this idea in a way that could be used by multiple
> applications and protocols?   It should not be hard to define a
> format for digital signatures that carries a few extra hash values,
> and allows a verifying party to check the signature on the message
> that they care about, while ignoring the rest.  The idea of
> reversing the client/server association between RSA
> encryption/decryption is a pragmatic way to help out servers, though
> it is tied to a specific algorithm (the results would be quite
> different for ECDH or ECDSA, say).  Both of those performance
> optimizations are definitely interesting, but I don't understand why
> the best way utilize those ideas would be through a new
> cryptographic protocol within the TCP layer.

The optimization is independent of tcpcrypt.  In fact, tcpcrypt's
standard doesn't mandate nor specify any authentication mechanisms -
it's left to the application.  Batch signing is just an example of
how one might authentication tcpcrypt sessions.  It can be done with
other protocols if they permit it.

Note that this optimization cannot be used in stock SSL because of SSL's
design.  SSL requires the server to perform an (expensive) private key
operation per client because each client sends over a unique encrypted                                       
pre-master secret which the server decrypts to prove its identity (i.e.,
that it knows the private key for the certificate it advertised to the
client).  So to leverage batch signing we need to design protocols that
allow for it, hence why we created tcpcrypt clean-slate.

We do have a drop-in replacement for OpenSSL that attempts to use
tcpcrypt+batch signing if able otherwise reverting to SSL.  This can be
used by many existing SSL applications without modifying them but just
replacing the system's SSL library.

> I also have some comments on some other points.  The USENIX Security
> paper mentions the goal of ubiquitous encryption (though the draft
> does not).  Requiring changes to the TCP stack would hinder
> deployment and work against the goal of ubiquity.

The protocol is designed with incremental deployment in mind which
hopefully will lead to ubiquitous encryption.  Specifically:

* It tries tcpcrypt and falls back to TCP gracefully.  The app doesn't
* have to know anything about tcpcrypt.

Sure, modifying the TCP stack hinders deployment.  So would modifying
all applications (which is potentially even more difficult).  We need to
modify something to get encryption, and for the reasons just mentioned
about incremental deployment we think TCP is the right place to do it.

> The draft describes the RSA public keys as "ephemeral", and the
> companion paper says that the protocol achieves forward secrecy.
> However, if it was really the case that a new RSA keypair was
> generated for each exchange, then the performance would be
> significantly worse than what is shown in the paper, because the
> cost of that operation is significantly higher than that of RSA
> decryption.   I think the claims and/or guidance to implementers
> needs to be clarified.

It's not perfect forward secrecy (i.e., one key per connection).  More
like one key per 10 minute window or whatever the system is configured
to.

> The Security Considerations section looks like boilerplate, while it
> seems that there is a lot to be discussed, such as the security
> properties of Session IDs.

Yes, we agree - this is just a first draft.  Well work on improving
that.  If this is taken on by the IETF, no doubt things we haven't
thought of will be pointed out.

> Is it possible to relate the protocol to a previously analyzed
> protocol?   It is similar to ISO/IEC 11770-3, in that it relies on
> public key encryption of nonces, without signatures.  Perhaps there
> is some analysis of that protocol, or of a protocol with cryptosuite
> negotiation, that could be leveraged.  The companion paper does have
> a brief analysis of the security of the protocol, but it would be
> good if it were possible to benefit from detailed analyses of all
> aspects of protocol security.  (I do realize that the analysis is
> made easier by the relative simplicity of the protocol; that's a
> good thing.)

We agree, and we'll work on this.

> The security analysis defines the parameter "k ~ 256 is the minimum
> of the min-entropy of a public key".  Surely that doesn't match the
> 2048-bit RSA examples in the paper?

The paper says: "where k ~ 256 is the minimum of the min-entropy of a
public key, or the length in bits of NS or NC."

NS and NC are random 256-bit values, so their min entropy is 256.  The
public key is a product of two 1,024-bit primes, so its min entropy is
much higher than 256.

The min entropy is just the probability of running the key generation
function twice and getting the same public key out the second time.
This has nothing to do with the difficulty of breaking RSA (which for
2,048-bit keys would be sort of equivalent to a 112-bit symmetric key).
The difficulty of breaking RSA is irrelevant to our reduction.  We are
saying that if you can break tcpcrypt, we can break the public key
algorithm or one of the other cryptographic functions in a "black box"
way, without regard to what the algorithms actually are.

> As a side note, I am surprised to see a proposal to add so much
> cryptographic functionality into the TCP standard, considering that
> not many years have passed since the transport area declined to add
> (much simpler) key transport functionality into TCP in support of
> TCP-AO.  Perhaps "Experimental" was intended, or perhaps I have
> missed or misunderstood some aspect of this work.

We think the perceived use case for TCP-AO was a replacement for TCP-MD5
in BGP sessions.  Of course TCP-AO is broader than that, but the
perceived use case may have influenced the previous decision.

From ekr@rtfm.com  Thu Jul 28 07:53:25 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00E7621F8A62 for <tsv-area@ietfa.amsl.com>; Thu, 28 Jul 2011 07:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fDdnJkJklcM6 for <tsv-area@ietfa.amsl.com>; Thu, 28 Jul 2011 07:53:24 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id E6B8B21F8AF5 for <tsv-area@ietf.org>; Thu, 28 Jul 2011 07:53:23 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1711676wwe.13 for <tsv-area@ietf.org>; Thu, 28 Jul 2011 07:53:22 -0700 (PDT)
Received: by 10.227.60.201 with SMTP id q9mr129835wbh.52.1311864800646; Thu, 28 Jul 2011 07:53:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.145.209 with HTTP; Thu, 28 Jul 2011 07:53:00 -0700 (PDT)
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 28 Jul 2011 10:53:00 -0400
Message-ID: <CABcZeBNg0eRou6q+XMJ_1YocMoasM9u8_OUXnU5bVfq3F-LmLw@mail.gmail.com>
Subject: SSL/TLS Performance Data
To: tsv-area@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Thu, 28 Jul 2011 07:56:50 -0700
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 14:53:25 -0000

Re: Mark's comments about SSL/TLS performance versus tcpcrypt
performance, it's worth reading:

http://www.imperialviolet.org/2010/06/25/overclocking-ssl.html

Relevant point:

In January this year (2010), Gmail switched to using HTTPS for
everything by default. Previously it had been introduced as an option,
but now all of our users use HTTPS to secure their email between their
browsers and Google, all the time. In order to do this we had to
deploy no additional machines and no special hardware. On our
production frontend machines, SSL/TLS accounts for less than 1% of the
CPU load, less than 10KB of memory per connection and less than 2% of
network overhead. Many people believe that SSL takes a lot of CPU time
and we hope the above numbers (public for the first time) will help to
dispel that.


-Ekr

From bob.briscoe@bt.com  Thu Jul 28 16:19:46 2011
Return-Path: <bob.briscoe@bt.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86C7C21F8B7B for <tsv-area@ietfa.amsl.com>; Thu, 28 Jul 2011 16:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.938
X-Spam-Level: 
X-Spam-Status: No, score=-2.938 tagged_above=-999 required=5 tests=[AWL=-0.408, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IRQt3iztDBTJ for <tsv-area@ietfa.amsl.com>; Thu, 28 Jul 2011 16:19:46 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by ietfa.amsl.com (Postfix) with ESMTP id 18D2711E811E for <tsv-area@ietf.org>; Thu, 28 Jul 2011 16:19:45 -0700 (PDT)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 29 Jul 2011 00:19:43 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by i2kc06-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Jul 2011 00:19:43 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 131189518219; Fri, 29 Jul 2011 00:19:42 +0100
Received: from MUT.jungle.bt.co.uk ([10.73.64.22]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id p6SNJd8F022546; Fri, 29 Jul 2011 00:19:40 +0100
Message-Id: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 28 Jul 2011 11:23:44 -0400
To: Janardhan Iyengar <jana.iyengar@gmail.com>
From: Bob Briscoe <bob.briscoe@bt.com>
Subject: LEDBAT doesn't help sharing network beyond home gateway
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 28 Jul 2011 23:19:43.0599 (UTC) FILETIME=[D540F7F0:01CC4D7C]
Cc: "ledbat@ietf.org" <ledbat@ietf.org>, tsv-area IETF list <tsv-area@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:19:46 -0000

Jana,

You asked the basis of what I just said in TSVAREA. I said in a 
residential network, LEDBAT won't yield to traffic sharing any queue 
upstream of your own home gateway queue.

LEDBAT's target delay is 150ms.

A typical shared link in such a network will be 1Gb/s.

150ms of queuing into a 1Gb/s link is 12,500 packets of queue (if 
1500B per pkt).

The buffer will not be this big (unless there's more bloat than 
anyone would expect)! Therefore LEDBAT will drive the queue off the 
end of its tail, just like TCP does. Therefore LEDAT is not designed 
to yield to others in such a queue into a higher speed link.

The root cause is the fixed 150ms target delay.

Nonetheless, I believe this design choice makes sense for LEDBAT 
_today_: you only yield to others in your own home. You don't yield 
to others in other homes.

If LEDBAT yielded to others, users would reject it. Evidence is on 
the Bittorrent community postings when uTP was 'imposed' on 
BitTorrent users - it was only accepted because it was shown that 
performance didn't suffer unless it was yielding to self.

We could design a LEDBAT-like protocol that yields to others in any 
queue. But no-one would want it (yet). Incidentally, a goal of ConEx 
is to incentivise deployment of LEDBAT-like protocols. The suffix 
'-like' means that they would benefit from yielding to anyone, not 
just your family in your home.


Bob



________________________________________________________________
Bob Briscoe,                                BT Innovate & Design 


From Rolf.Winter@neclab.eu  Thu Jul 28 16:30:14 2011
Return-Path: <Rolf.Winter@neclab.eu>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F18C11E80C8; Thu, 28 Jul 2011 16:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.389
X-Spam-Level: 
X-Spam-Status: No, score=-102.389 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id av11jIyuQEmc; Thu, 28 Jul 2011 16:30:13 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id C746211E80A2; Thu, 28 Jul 2011 16:30:12 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 8C5C828000329; Fri, 29 Jul 2011 01:30:11 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office.hd)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CqFgvU4MLIuo; Fri, 29 Jul 2011 01:30:11 +0200 (CEST)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 66BF628000198; Fri, 29 Jul 2011 01:29:51 +0200 (CEST)
Received: from DAPHNIS.office.hd ([169.254.2.20]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Fri, 29 Jul 2011 01:29:30 +0200
From: Rolf Winter <Rolf.Winter@neclab.eu>
To: Bob Briscoe <bob.briscoe@bt.com>, Janardhan Iyengar <jana.iyengar@gmail.com>
Subject: RE: [ledbat] LEDBAT doesn't help sharing network beyond home gateway
Thread-Topic: [ledbat] LEDBAT doesn't help sharing network beyond home gateway
Thread-Index: AQHMTXzjahdOl9p7WUmuqzdg87JclZUCYPrg
Date: Thu, 28 Jul 2011 23:29:29 +0000
Message-ID: <791AD3077F94194BB2BDD13565B6295D1D034AF5@DAPHNIS.office.hd>
References: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
In-Reply-To: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.7.0.197]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ledbat@ietf.org" <ledbat@ietf.org>, tsv-area IETF list <tsv-area@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:30:14 -0000

One clarification. The target is 100ms, can be less, but not more. The "can=
 be less" part is to cater for the future. The cannot be more is to make su=
re you cannot be unfair unless you chose to be non-standards compliant.

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014=20


> -----Original Message-----
> From: ledbat-bounces@ietf.org [mailto:ledbat-bounces@ietf.org] On
> Behalf Of Bob Briscoe
> Sent: Donnerstag, 28. Juli 2011 17:24
> To: Janardhan Iyengar
> Cc: ledbat@ietf.org; tsv-area IETF list
> Subject: [ledbat] LEDBAT doesn't help sharing network beyond home
> gateway
>=20
> Jana,
>=20
> You asked the basis of what I just said in TSVAREA. I said in a
> residential network, LEDBAT won't yield to traffic sharing any queue
> upstream of your own home gateway queue.
>=20
> LEDBAT's target delay is 150ms.
>=20
> A typical shared link in such a network will be 1Gb/s.
>=20
> 150ms of queuing into a 1Gb/s link is 12,500 packets of queue (if
> 1500B per pkt).
>=20
> The buffer will not be this big (unless there's more bloat than
> anyone would expect)! Therefore LEDBAT will drive the queue off the
> end of its tail, just like TCP does. Therefore LEDAT is not designed
> to yield to others in such a queue into a higher speed link.
>=20
> The root cause is the fixed 150ms target delay.
>=20
> Nonetheless, I believe this design choice makes sense for LEDBAT
> _today_: you only yield to others in your own home. You don't yield
> to others in other homes.
>=20
> If LEDBAT yielded to others, users would reject it. Evidence is on
> the Bittorrent community postings when uTP was 'imposed' on
> BitTorrent users - it was only accepted because it was shown that
> performance didn't suffer unless it was yielding to self.
>=20
> We could design a LEDBAT-like protocol that yields to others in any
> queue. But no-one would want it (yet). Incidentally, a goal of ConEx
> is to incentivise deployment of LEDBAT-like protocols. The suffix
> '-like' means that they would benefit from yielding to anyone, not
> just your family in your home.
>=20
>=20
> Bob
>=20
>=20
>=20
> ________________________________________________________________
> Bob Briscoe,                                BT Innovate & Design
>=20
> _______________________________________________
> ledbat mailing list
> ledbat@ietf.org
> https://www.ietf.org/mailman/listinfo/ledbat

From muraris@microsoft.com  Thu Jul 28 16:59:28 2011
Return-Path: <muraris@microsoft.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE05711E80C8; Thu, 28 Jul 2011 16:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.343
X-Spam-Level: 
X-Spam-Status: No, score=-110.343 tagged_above=-999 required=5 tests=[AWL=0.256, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tv2vXNfW3+S4; Thu, 28 Jul 2011 16:59:28 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id 7234621F8A23; Thu, 28 Jul 2011 16:59:28 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 28 Jul 2011 16:59:28 -0700
Received: from TK5EX14MBXC298.redmond.corp.microsoft.com ([169.254.1.177]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.01.0323.002; Thu, 28 Jul 2011 16:59:27 -0700
From: Murari Sridharan <muraris@microsoft.com>
To: Bob Briscoe <bob.briscoe@bt.com>, Janardhan Iyengar <jana.iyengar@gmail.com>
Subject: RE: LEDBAT doesn't help sharing network beyond home gateway
Thread-Topic: LEDBAT doesn't help sharing network beyond home gateway
Thread-Index: AQHMTXzgQ/cdPh1c+kS+bY60FnzEqpUCaZYQ
Date: Thu, 28 Jul 2011 23:59:26 +0000
Message-ID: <EF5EF2B13ED09B4F871D9A0DBCA463C216B9A9C0@TK5EX14MBXC298.redmond.corp.microsoft.com>
References: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
In-Reply-To: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.76]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ledbat@ietf.org" <ledbat@ietf.org>, tsv-area IETF list <tsv-area@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 23:59:29 -0000

Bob, agree & great point.=20

-----Original Message-----
From: tsv-area-bounces@ietf.org [mailto:tsv-area-bounces@ietf.org] On Behal=
f Of Bob Briscoe
Sent: Thursday, July 28, 2011 8:24 AM
To: Janardhan Iyengar
Cc: ledbat@ietf.org; tsv-area IETF list
Subject: LEDBAT doesn't help sharing network beyond home gateway

Jana,

You asked the basis of what I just said in TSVAREA. I said in a residential=
 network, LEDBAT won't yield to traffic sharing any queue upstream of your =
own home gateway queue.

LEDBAT's target delay is 150ms.

A typical shared link in such a network will be 1Gb/s.

150ms of queuing into a 1Gb/s link is 12,500 packets of queue (if 1500B per=
 pkt).

The buffer will not be this big (unless there's more bloat than anyone woul=
d expect)! Therefore LEDBAT will drive the queue off the end of its tail, j=
ust like TCP does. Therefore LEDAT is not designed to yield to others in su=
ch a queue into a higher speed link.

The root cause is the fixed 150ms target delay.

Nonetheless, I believe this design choice makes sense for LEDBAT
_today_: you only yield to others in your own home. You don't yield to othe=
rs in other homes.

If LEDBAT yielded to others, users would reject it. Evidence is on the Bitt=
orrent community postings when uTP was 'imposed' on BitTorrent users - it w=
as only accepted because it was shown that performance didn't suffer unless=
 it was yielding to self.

We could design a LEDBAT-like protocol that yields to others in any queue. =
But no-one would want it (yet). Incidentally, a goal of ConEx is to incenti=
vise deployment of LEDBAT-like protocols. The suffix '-like' means that the=
y would benefit from yielding to anyone, not just your family in your home.


Bob



________________________________________________________________
Bob Briscoe,                                BT Innovate & Design=20



From arvid@cs.umu.se  Thu Jul 28 19:35:47 2011
Return-Path: <arvid@cs.umu.se>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 516B521F8666; Thu, 28 Jul 2011 19:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nQq1aT1NUWWE; Thu, 28 Jul 2011 19:35:46 -0700 (PDT)
Received: from mail.acc.umu.se (mail.acc.umu.se [IPv6:2001:6b0:e:2018::156]) by ietfa.amsl.com (Postfix) with ESMTP id E427521F85DE; Thu, 28 Jul 2011 19:35:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by amavisd-new (Postfix) with ESMTP id 433F189F; Fri, 29 Jul 2011 04:35:42 +0200 (MEST)
X-Virus-Scanned: amavisd-new at acc.umu.se
Received: from mao.acc.umu.se (mao.acc.umu.se [130.239.18.154]) by mail.acc.umu.se (Postfix) with ESMTP id 3C29D89E; Fri, 29 Jul 2011 04:35:41 +0200 (MEST)
Received: by mao.acc.umu.se (Postfix, from userid 3027) id 38E781009B; Fri, 29 Jul 2011 04:34:40 +0200 (CEST)
Received: from 38.99.42.130 ([38.99.42.130])  by puss.acc.umu.se (IMP) with HTTP  for <arvid@mail.cs.umu.se>; Fri, 29 Jul 2011 04:34:40 +0200
Message-ID: <1311906880.4e321c4026475@puss.acc.umu.se>
Date: Fri, 29 Jul 2011 04:34:40 +0200
From: arvid@cs.umu.se
To: Sampo Syreeni <decoy@iki.fi>
Subject: Re: [ledbat] LEDBAT doesn't help sharing network beyond home gateway
References: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk> <Pine.LNX.4.64.1107290408530.15843@lakka.kapsi.fi>
In-Reply-To: <Pine.LNX.4.64.1107290408530.15843@lakka.kapsi.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Mailman-Approved-At: Thu, 28 Jul 2011 20:27:42 -0700
Cc: Janardhan Iyengar <jana.iyengar@gmail.com>, "ledbat@ietf.org" <ledbat@ietf.org>, tsv-area IETF list <tsv-area@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 02:35:47 -0000

Quoting Sampo Syreeni <decoy@iki.fi>:

> On 2011-07-28, Bob Briscoe wrote:
> 
> > I said in a residential network, LEDBAT won't yield to traffic sharing 
> > any queue upstream of your own home gateway queue.
> >
> > LEDBAT's target delay is 150ms.

I thought the LEDBAT target delay was 25 ms, but I might have missed some
update. In BitTorrent's uTP it's 100 ms right now.

> Target delay, but also a one designed to mimic the minimum delay over 
> the whole path? No? A users's upstream cable modem being the most 
> typical and biggest part of that, but still, isn't the protocol about 
> the whole?

It's important to understand what "target delay" means. In LEDBAT, it refers to
the delay on top of the lowest ever seen one-way latency from the source to the
destination. It does not include any fixed latency (such as the fixed latency
you have in routers for handling packets in each hop nor the speed of light),
the variable in the one-way latency is essentially entirely the time a packet
spends sitting in buffers. LEDBAT does not care about which buffer or where the
buffer is (whether it's your router, your modem, your ISP's router or your
destination's ISPs router etc.).

> Shouldn't it then in theory be that LEDBAT quenches towards the minimum 
> total delay, regardless of where the bottleneck might be? Any higher up, 
> faster, less congested buffers ought to be totally neglected in the 
> process because the lower, more filled up dominate the e2e delay 
> calculation?

That sounds like a correct statement.

> If not, then the quenching ought to happen because of the more congested 
> link/filled up buffer, that is *now* causing the extra delay beoynd the 
> minimum sensed.
> 
> > The root cause is the fixed 150ms target delay.
> 
> So what I (we?) am missing is that with very fast networks the protocol 
> should be able to asymptotically go to zero latency, while staying nice 
> and crowd-stable? Are there other, statistical considerations beyond 
> this?

If no buffer along the path can fit the target-delay amount of bytes, LEDBAT
would essentially behave like TCP, and (essentially) be just as fair as TCP is.

> > If LEDBAT yielded to others, users would reject it.
> 
> They absolutely would not. In fact, they don't: it's in current use and 
> is rapidly being adopted by the numbers, as uTP, within uTorrent (and 
> others).

Right. It just happens to be people's modems that are the bottlenecks
(unsurprisingly).

-- 
Arvid Norberg

From decoy@iki.fi  Thu Jul 28 18:20:08 2011
Return-Path: <decoy@iki.fi>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE52011E810E; Thu, 28 Jul 2011 18:20:08 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oC8nLsnfIFxT; Thu, 28 Jul 2011 18:20:08 -0700 (PDT)
Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) by ietfa.amsl.com (Postfix) with ESMTP id B8C6911E8092; Thu, 28 Jul 2011 18:20:07 -0700 (PDT)
Received: from lakka.kapsi.fi ([2001:1bc8:1004::1] ident=Debian-exim) by mail.kapsi.fi with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <decoy@iki.fi>) id 1Qmbk6-0001mp-9Q; Fri, 29 Jul 2011 04:19:58 +0300
Received: from decoy (helo=localhost) by lakka.kapsi.fi with local-esmtp (Exim 4.72) (envelope-from <decoy@iki.fi>) id 1Qmbk6-0001Ii-5s; Fri, 29 Jul 2011 04:19:58 +0300
Date: Fri, 29 Jul 2011 04:19:57 +0300 (EEST)
From: Sampo Syreeni <decoy@iki.fi>
Sender: decoy@kapsi.fi
To: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: [ledbat] LEDBAT doesn't help sharing network beyond home gateway
In-Reply-To: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
Message-ID: <Pine.LNX.4.64.1107290408530.15843@lakka.kapsi.fi>
References: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-SA-Exim-Connect-IP: 2001:1bc8:1004::1
X-SA-Exim-Mail-From: decoy@iki.fi
X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false
X-Mailman-Approved-At: Thu, 28 Jul 2011 20:27:51 -0700
Cc: Janardhan Iyengar <jana.iyengar@gmail.com>, "ledbat@ietf.org" <ledbat@ietf.org>, tsv-area IETF list <tsv-area@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 01:20:08 -0000

On 2011-07-28, Bob Briscoe wrote:

> I said in a residential network, LEDBAT won't yield to traffic sharing 
> any queue upstream of your own home gateway queue.
>
> LEDBAT's target delay is 150ms.

Target delay, but also a one designed to mimic the minimum delay over 
the whole path? No? A users's upstream cable modem being the most 
typical and biggest part of that, but still, isn't the protocol about 
the whole?

Shouldn't it then in theory be that LEDBAT quenches towards the minimum 
total delay, regardless of where the bottleneck might be? Any higher up, 
faster, less congested buffers ought to be totally neglected in the 
process because the lower, more filled up dominate the e2e delay 
calculation?

If not, then the quenching ought to happen because of the more congested 
link/filled up buffer, that is *now* causing the extra delay beoynd the 
minimum sensed.

> The root cause is the fixed 150ms target delay.

So what I (we?) am missing is that with very fast networks the protocol 
should be able to asymptotically go to zero latency, while staying nice 
and crowd-stable? Are there other, statistical considerations beyond 
this?

> If LEDBAT yielded to others, users would reject it.

They absolutely would not. In fact, they don't: it's in current use and 
is rapidly being adopted by the numbers, as uTP, within uTorrent (and 
others).

> We could design a LEDBAT-like protocol that yields to others in any 
> queue. But no-one would want it (yet). Incidentally, a goal of ConEx 
> is to incentivise deployment of LEDBAT-like protocols. The suffix 
> '-like' means that they would benefit from yielding to anyone, not 
> just your family in your home.

Yes. So I at least am missing something. I'm sorry to ask for looking a 
bit stupid, but... What *am* I missing, really?
-- 
Sampo Syreeni, aka decoy - decoy@iki.fi, http://decoy.iki.fi/front
+358-50-5756111, 025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2

From swmike@swm.pp.se  Thu Jul 28 22:49:51 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43B8021F8922; Thu, 28 Jul 2011 22:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level: 
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKuKwXDQgRgL; Thu, 28 Jul 2011 22:49:50 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA5921F891F; Thu, 28 Jul 2011 22:49:50 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D11199C; Fri, 29 Jul 2011 07:49:49 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id CD7159A; Fri, 29 Jul 2011 07:49:49 +0200 (CEST)
Date: Fri, 29 Jul 2011 07:49:49 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: LEDBAT doesn't help sharing network beyond home gateway
In-Reply-To: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
Message-ID: <alpine.DEB.2.00.1107290748000.26694@uplift.swm.pp.se>
References: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Janardhan Iyengar <jana.iyengar@gmail.com>, "ledbat@ietf.org" <ledbat@ietf.org>, tsv-area IETF list <tsv-area@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 05:49:51 -0000

On Thu, 28 Jul 2011, Bob Briscoe wrote:

> LEDBAT's target delay is 150ms.

What about loss? If there is a RED profile that starts dropping at 30ms 
and has 100% drop at 100ms, would LEDBAT behave mostly like TCP?

I agree with other posters in this thread that at 100ms, LEDBAT will only 
lessen congestion on hour own link, because most of the time a provider 
core will never buffer 100ms, it just doesn't make sense.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From richard_woundy@cable.comcast.com  Thu Jul 28 20:57:11 2011
Return-Path: <richard_woundy@cable.comcast.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAD2F21F8639; Thu, 28 Jul 2011 20:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.399
X-Spam-Level: 
X-Spam-Status: No, score=-106.399 tagged_above=-999 required=5 tests=[AWL=2.064, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8yhS1-BSjeS9; Thu, 28 Jul 2011 20:57:11 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by ietfa.amsl.com (Postfix) with ESMTP id 844F021F85B9; Thu, 28 Jul 2011 20:57:09 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.135534643; Thu, 28 Jul 2011 23:57:03 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%11]) with mapi id 14.01.0289.001; Thu, 28 Jul 2011 23:57:03 -0400
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "arvid@cs.umu.se" <arvid@cs.umu.se>, Sampo Syreeni <decoy@iki.fi>
Subject: RE: [ledbat] LEDBAT doesn't help sharing network beyond home gateway
Thread-Topic: [ledbat] LEDBAT doesn't help sharing network beyond home gateway
Thread-Index: AQHMTXzcinrsN+47UUa+u48s5QEF65UCw1WAgAAU4QD//9N3YA==
Date: Fri, 29 Jul 2011 03:57:02 +0000
Message-ID: <1CA25301D2219F40B3AA37201F0EACD1135DF0C7@PACDCEXMB05.cable.comcast.com>
References: <201107282319.p6SNJd8F022546@bagheera.jungle.bt.co.uk> <Pine.LNX.4.64.1107290408530.15843@lakka.kapsi.fi> <1311906880.4e321c4026475@puss.acc.umu.se>
In-Reply-To: <1311906880.4e321c4026475@puss.acc.umu.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [76.96.111.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 29 Jul 2011 05:24:29 -0700
Cc: Janardhan Iyengar <jana.iyengar@gmail.com>, "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, "ledbat@ietf.org" <ledbat@ietf.org>, tsv-area IETF list <tsv-area@ietf.org>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 03:57:12 -0000

> I thought the LEDBAT target delay was 25 ms, but I might have missed some=
 update. In BitTorrent's uTP it's 100 ms right now.

The LEDBAT target delay was increased from 25 msec to 100 msec in version -=
02, to match the uTP implementation.

-----Original Message-----
From: ledbat-bounces@ietf.org [mailto:ledbat-bounces@ietf.org] On Behalf Of=
 arvid@cs.umu.se
Sent: Thursday, July 28, 2011 10:35 PM
To: Sampo Syreeni
Cc: Janardhan Iyengar; ledbat@ietf.org; tsv-area IETF list
Subject: Re: [ledbat] LEDBAT doesn't help sharing network beyond home gatew=
ay

Quoting Sampo Syreeni <decoy@iki.fi>:

> On 2011-07-28, Bob Briscoe wrote:
>=20
> > I said in a residential network, LEDBAT won't yield to traffic sharing=
=20
> > any queue upstream of your own home gateway queue.
> >
> > LEDBAT's target delay is 150ms.

I thought the LEDBAT target delay was 25 ms, but I might have missed some
update. In BitTorrent's uTP it's 100 ms right now.

> Target delay, but also a one designed to mimic the minimum delay over=20
> the whole path? No? A users's upstream cable modem being the most=20
> typical and biggest part of that, but still, isn't the protocol about=20
> the whole?

It's important to understand what "target delay" means. In LEDBAT, it refer=
s to
the delay on top of the lowest ever seen one-way latency from the source to=
 the
destination. It does not include any fixed latency (such as the fixed laten=
cy
you have in routers for handling packets in each hop nor the speed of light=
),
the variable in the one-way latency is essentially entirely the time a pack=
et
spends sitting in buffers. LEDBAT does not care about which buffer or where=
 the
buffer is (whether it's your router, your modem, your ISP's router or your
destination's ISPs router etc.).

> Shouldn't it then in theory be that LEDBAT quenches towards the minimum=20
> total delay, regardless of where the bottleneck might be? Any higher up,=
=20
> faster, less congested buffers ought to be totally neglected in the=20
> process because the lower, more filled up dominate the e2e delay=20
> calculation?

That sounds like a correct statement.

> If not, then the quenching ought to happen because of the more congested=
=20
> link/filled up buffer, that is *now* causing the extra delay beoynd the=20
> minimum sensed.
>=20
> > The root cause is the fixed 150ms target delay.
>=20
> So what I (we?) am missing is that with very fast networks the protocol=20
> should be able to asymptotically go to zero latency, while staying nice=20
> and crowd-stable? Are there other, statistical considerations beyond=20
> this?

If no buffer along the path can fit the target-delay amount of bytes, LEDBA=
T
would essentially behave like TCP, and (essentially) be just as fair as TCP=
 is.

> > If LEDBAT yielded to others, users would reject it.
>=20
> They absolutely would not. In fact, they don't: it's in current use and=20
> is rapidly being adopted by the numbers, as uTP, within uTorrent (and=20
> others).

Right. It just happens to be people's modems that are the bottlenecks
(unsurprisingly).

--=20
Arvid Norberg
_______________________________________________
ledbat mailing list
ledbat@ietf.org
https://www.ietf.org/mailman/listinfo/ledbat

From bittau@gmail.com  Fri Jul 29 18:47:36 2011
Return-Path: <bittau@gmail.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3ED711E8073; Fri, 29 Jul 2011 18:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.119
X-Spam-Level: 
X-Spam-Status: No, score=-1.119 tagged_above=-999 required=5 tests=[AWL=-2.107, BAYES_00=-2.599, FRT_STOCK2=3.988, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KrUPTcfg+YAc; Fri, 29 Jul 2011 18:47:36 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id EE6675E8020; Fri, 29 Jul 2011 18:47:35 -0700 (PDT)
Received: by iye7 with SMTP id 7so5545578iye.31 for <multiple recipients>; Fri, 29 Jul 2011 18:47:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-echelon:user-agent; bh=CwB/EvwkzDFnGaTSioC+hbuUUczMqx4xM5kUNFKcP94=; b=m2BTsVz7u3BO5RJqDXD8jLmKcxOIkf/yIK+eJ/MrgiAx25Qy+bxZKMTYhqOA+lErGj aet6bozrfZ3p4yzcPc7gf6XdZflUJv9QWqtFpIi+pb41R3GUt5DkivIpIStwRF+bVTtk /lgQoFpqb796w+k9SPmci30eCNgVWjmztwuxU=
Received: by 10.42.97.68 with SMTP id m4mr1521367icn.292.1311990455386; Fri, 29 Jul 2011 18:47:35 -0700 (PDT)
Received: from tapir.cs.ucl.ac.uk (sorbox.scs.stanford.edu [171.66.3.197]) by mx.google.com with ESMTPS id s2sm3530668icw.5.2011.07.29.18.47.31 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jul 2011 18:47:32 -0700 (PDT)
Sender: Andrea Bittau <bittau@gmail.com>
Received: by tapir.cs.ucl.ac.uk (Postfix, from userid 0) id 1FE634810172; Fri, 29 Jul 2011 18:45:44 -0700 (PDT)
Date: Fri, 29 Jul 2011 18:45:44 -0700
From: Andrea Bittau <bittau@cs.stanford.edu>
To: "David A. McGrew" <david.a.mcgrew@mindspring.com>
Subject: Re: [saag] fyi: tcpcrypt draft
Message-ID: <20110730014544.GM3751@shorty>
References: <4DC6C56D.6040709@ieca.com> <D1CCED3D-C041-4DA2-B999-D3EF7FC889D0@cisco.com> <20110727184256.GA3690@shorty> <8A00B447-53C3-44D0-8238-8DAAE44688CB@mindspring.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8A00B447-53C3-44D0-8238-8DAAE44688CB@mindspring.com>
X-Echelon: Bush Bomb War KGB
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: tcpcrypt@scs.stanford.edu, Sean Turner <turners@ieca.com>, tsv-area@ietf.org, saag@ietf.org
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jul 2011 01:47:37 -0000

On Thu, Jul 28, 2011 at 07:33:05AM -0700, David A. McGrew wrote:
> A lot of work has been done on using IPsec to solve these problems,
> and it is important to explain in detail how tcpcrypt improves on
> this work.  Besides the opportunistic encryption effort, there is
> BTNS (draft-ietf-btns-channel-binding-api-00 defines channel
> bindings for IPsec, for instance), RFC 3947 for running IPsec over
> NAT.  (Half joking: would the configuration of
> draft-ietf-ipsec-internet-key-00 with NAT-T solve all or most these
> problems?)

tcpcrypt makes incremental deployment easier because probing is built
into existing packets and fallback comes at no extrea cost.   When a SYN
packet is sent out and tcpcrypt is not supported at the other end, we
can fallback to regular tcpcrypt at no extra cost - just carry on with a
vanilla TCP handshake.  How would this work with BTNS or IPSec?  Do you
probe for IPSec (and then probe for NAT-T), wait for a timeout, and then
send a TCP SYN?  If so, it adds network overhead (extra packets) and
latency (probe timeout).

tcpcrypt also has less protocol (space) overhead.  NAT-T requires
encapsulating IP in UDP, and NAT seems like a common deployment
scenario.  It also requires opening more ports on a firewall and
configuring additional services (NAT-T).

> What TCP applications can't use TLS?   Do you mean that some apps
> don't use TLS in current implementations, or that there is some
> basic incompatibility?

There's a bootstrap problem.  If I have SMTP on TCP/25 I have to assume
it's clear-text (I can't send an SSL handshake packet).  Thankfully,
SMTP is an extensible protocol and I can send STARTTLS and then go on
with SSL.  If the protocol didn't permit any "options" / commands, I'd
be stuck to plain-text.  I'd have to allocate a new port.  That makes
incremental deployment harder - do I send two SYNs?

> What about running TCP on top of DTLS?   That would protect the TCP
> session, while keeping the crypto separate from the TCP stack.

Same answer as per BTNS and NAT-T - we can efficiently incrementally
deploy and have less protocol overhead.

> 1.  How easy to configure will tcpcrypt be once it supports mutual
> authentication, the enforcement of configurable security policies,
> and crypto algorithm agility (e.g. ECDH and ECDSA)?

Authentication is left to the application, so tcpcrypt will support
authentication only if the application supports it.  If the application
supports it, then a mechanism is already in place, e.g., htpasswd in
Apache for passwords.  So in the case of Apache, it'll include
tcpcrypt's session id when doing http digest authentication, for
example.

We're also working on an authentication library that attempts to
authenticate tcpcrypt using DNSSEC+DANE that can be used by all apps if
DANE is deployed.  The configuration will require storing a certificate
fingerprint in DNS.

We expect that most applications (e.g., the ones running clear-text                                          
today) won't care about the crypto algorithms used in tcpcrypt's
handshake.  So the security policy will be set system-wide (e.g., allow
only RSA, SHA1 or whatever).  For security concious applications it'll
be a setsockopt and presumably those applications already have a
configuration file for whatever the already use today for crypto.

> 2.  The comparison of tcpcrypt to TLS is only considering the RSA
> ciphersuites in the latter protocol.  The efficiency and security
> properties of other ciphersuites are quite different.

Yes, but we expect tcpcrypt to be no worse (or better) than TLS.
tcpcrypt fundamentally does however have lower latency for conncection
establishment compared to TLS due to fewer RTTs needed in negotiating a
key (we leverage the 3-way handshake and add only an extra leg),
especially when session caching.

> 3.  Reversing the client and server public/private key operations in
> tcpcrypt, which is used to make the protocol more scalable, is
> applicable only to the RSA algorithm.   In particular, the situation
> with elliptic curve cryptography is quite different.  This raises
> some questions: how does tcpcrypt with RSA compare to an ECDH/ECDSA
> TLS ciphersuite, say, at security levels of 128, 192, or 256 bits?
> How does tcpcrypt perform with other algorithms?   Given the
> interest in ECC as a future direction for cryptography, these
> questions deserve some thought.

Yes, we'll implement those but we do not expect tcpcrypt's performance
to be much different from a TLS implementation - we both do the same
thing (e.g., ECDH).

> What you are describing here is true for the RSA ciphersuites in
> SSL, but is not true for the Diffie-Hellman ciphersuites, or the
> ECDH ones (see Section 7.4.2 of RFC 5246 for instance).

tcpcrypyt's main goal is to be deployed ubiquitously.  Improved
performance in one case is only a bonus.  It has a bunch of other
advantages (single integrated mechanism, incrementally deployable) apart
from RSA performance.

> Why is graceful fallback easier at the TCP layer than at another
> layer?   And if there is some mechanism within TCP that facilitates
> fallback, would it be possible to use that mechanism in conjunction
> with a cryptographic protocol external to TCP?  That last option
> would minimize the impact to TCP implementations, meaning less new
> code inside kernels, and fewer states, and so on.

Gracefully, and efficient, I should add.  The problem is detecting
whether the other end supports crypto mechanism X.  At a below-transport
layer, we'd have to send our IP packet, wait for a timeout, and then
send a SYN.  At a transport layer we're sending out a SYN so we can
easily piggyback options (perfect!).  At an application layer what's the
first thing we send?  STARTTLS?  Does the application-layer protocol
allow such new commands or will it drop the command?

The minimum TCP mechanism needed for a graceful and efficient fallback
is a TCP option in the SYN.  So, tcpcrypt-lite would modify a kernel
with a setsockopt(CRYPTO_OPTION) to include the CRYPTO option in a SYN
and getsockopt(CRYPTO_OPTION) to see if the CRYPTO option was echoed in
the SYN-ACK.  At that point SSL_accept() can be called.  But we lose all
TCP header MACing - e.g., someone can RST our connection.  TCP AO
suggests that MACing TCP headers is important so crypto protocols should
do that (hence why we live in the transport layer).  Also, we can
leverage the existing 3-way handshake to get a head start on crypto
negotiations.  Sesison caching completes within the three way handshake.

> If the RSA keypair is generated using a pseudorandom process (and
> there are standards for doing that), the min entropy could be lower.
> 
> But if it is adequate to have the entropy show up in the nonces, the
> min-entropy of the key would be a moot point.

The pseudo-random generator has to have enough state to generate prime
numbers with min entropy 256.  Depending on the prime number generator,
this might, for instance, require something on the order of 256 + ceil
(log_2 (log_e (2 ^ 1024))) or 266 bits.  We assume most RSA
implementations would have more random state than that.
