Re: [nat66] NPTv6 deals with "packets", not with "datagrams" - to be corrected after draft-14

Scott Brim <scott.brim@gmail.com> Tue, 03 May 2011 20:55 UTC

Return-Path: <scott.brim@gmail.com>
X-Original-To: nat66@ietfa.amsl.com
Delivered-To: nat66@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36FD1E0713; Tue, 3 May 2011 13:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.341
X-Spam-Level:
X-Spam-Status: No, score=-103.341 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 cWwoiWIiPKkD; Tue, 3 May 2011 13:55:19 -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 A0364E069A; Tue, 3 May 2011 13:55:19 -0700 (PDT)
Received: by iyn15 with SMTP id 15so482187iyn.31 for <multiple recipients>; Tue, 03 May 2011 13:55:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=MhCKnpbwSJJAmn1JxL93mPkC+8gLVOKcDXH5CwcVehs=; b=RgW/BjrEZ5qM91bY3feNyBr7CBvsmdB9aENr3R7GWlsal5gzB5GcdMRc+jyy4ql0tE pz2/+66zmhHCsEf/uIAI9hJ2wI3Ot8NwdSn4D5iuLI+3W5bayrOg+QMPDpGgfoDWVxEx CA2UXN8CxJAMaBON1qFr3iFt3ckFyXcSkhxbg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=XSqQEUVLbNCq1+VFMUfRunMR4G2sX8ofrYuTxKePLk4+ncUUSCw4k3OF5QD55Jg194 frYJfgm1D+0Pg0GFKg0YXvVfmQo0wZPjW2E+/k4ziavTG5Paq/gzuY6kom+ngMrAFZRN LywSP6UnhLs2mBsTLVXzdf67e/02syoF3Oglk=
Received: by 10.42.178.10 with SMTP id bk10mr490063icb.167.1304456119079; Tue, 03 May 2011 13:55:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.30.73 with HTTP; Tue, 3 May 2011 13:54:59 -0700 (PDT)
In-Reply-To: <038FC1DC-E0B3-4646-98F1-BFA637BED48D@cisco.com>
References: <20110314063002.28048.29694.idtracker@localhost> <19F3A4CD-F39C-4F17-A6E9-7AA8AFBC6B3B@cisco.com> <CF8367A6-F303-43D7-99C6-D40D1DD5D5D9@free.fr> <87C8BBB5-2B11-412E-B788-1538CBE03FB4@cisco.com> <067FF1C8-985D-49B7-AF8D-86A0F337CB9D@free.fr> <B6BD718F-6940-4ECE-833C-670052DB3998@cisco.com> <19D548C2-0644-4E0B-B725-442D0877E044@free.fr> <7F2F3C67-96CC-428E-9453-3EE0480CAFD5@cisco.com> <349CFE54-B2EB-4D79-91BB-0AE7DDA03988@free.fr> <038FC1DC-E0B3-4646-98F1-BFA637BED48D@cisco.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 03 May 2011 16:54:59 -0400
Message-ID: <BANLkTi=_BtBYugWUCJJdnoRcd0heLhsnDQ@mail.gmail.com>
To: Fred Baker <fred@cisco.com>
Content-Type: multipart/alternative; boundary="90e6ba6e8d5a9a549104a2655b0f"
Cc: IESG <iesg@ietf.org>, NAT66 HappyFunBall <nat66@ietf.org>
Subject: Re: [nat66] NPTv6 deals with "packets", not with "datagrams" - to be corrected after draft-14
X-BeenThere: nat66@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for discussion of IPv6-to-IPv6 NAT." <nat66.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nat66>, <mailto:nat66-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nat66>
List-Post: <mailto:nat66@ietf.org>
List-Help: <mailto:nat66-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 20:55:20 -0000

Remi: One of the essential characteristics of a "datagram" is that it
carries all information necessary for it to be delivered _across a network_
... that is, it contains information that the network can use for routing
and forwarding decisions.  The network, i.e. the Internet.  The functional
determination of whether something is a datagram is made in the network, at
the IP layer, by network components.

Dave: "user datagram" as in UDP refers to exposing the datagram interface to
the user.  "This User Datagram  Protocol (UDP) is defined to make available
a datagram mode of packet-switched computer communication": a "datagram
mode" is "made available", that is, the user can send datagrams directly
instead of offering a stream or a file that is magically chopped up into
datagrams for him.  "User datagram" is not a new meaning of datagram.

OK?

swb