Re: RFC 5321bis / 2821ter

SM <sm@resistor.net> Mon, 26 January 2009 20:31 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0QKVpwF034599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Jan 2009 13:31:51 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n0QKVpWN034598; Mon, 26 Jan 2009 13:31:51 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0QKVoOs034592 for <ietf-smtp@imc.org>; Mon, 26 Jan 2009 13:31:50 -0700 (MST) (envelope-from sm@resistor.net)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.4.Alpha0/8.14.4.Alpha0) with ESMTP id n0QKVbro018875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Jan 2009 12:31:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1233001906; x=1233088306; bh=n909plHwc5HQPhgOpvrtaG3c7XfuW15itbpn8Ff2IPM=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=rNxhBEEuhlbVXzhTt7vy/RZYc5WA95xzc2CuHuEDNvmiNlQyRv5yCtzIdBVqCnLwe nPQh72jLyCAq/b1wmlfkaXNKlhHlmw3vbdUxV8SowYieCj1VSrrQ7wCIv48MNY+ZOd d1/mlbGd/do7PGd7QhEX8/Dge1sUDkgSBzTxnKyM=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=jMjIabSZA59+e0c5r1BbnHnTdmGpXMVM3CjVkkaDwp4PO+078khsWh4gy8BwG1ENR +Tzmjnnhz+eKe7iPOGElyiT79nMvSTt5Wm2DAEcNcgqrCaCcR1nyZMYcPQbxqkHPd5e ORX3lOEr61Bqs67xWAcwUV5NtTg48Pb3o9xeNvc=
Message-Id: <6.2.5.6.2.20090126110017.02f261e0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 26 Jan 2009 12:01:45 -0800
To: Jeff Macdonald <jmacdonald@e-dialog.com>
From: SM <sm@resistor.net>
Subject: Re: RFC 5321bis / 2821ter
Cc: ietf-smtp@imc.org
In-Reply-To: <20090126181722.GN6078@jmac.e-dialog.com>
References: <E5EF288BD222F5BA20C735BD@PST.JCK.COM> <497980AA.2060706@es2eng.com> <C4ZHRHThnSMjwwDOZ03z0w.md5@lochnagar.oryx.com> <4979B5F2.9010102@pscs.co.uk> <WBwvOp9JIdw2SWc1HYscRg.md5@lochnagar.oryx.com> <4979D903.1060705@pscs.co.uk> <5.2.1.1.0.20090123140212.03ed3fb0@plus.pop.mail.yahoo.com> <51104ACCD26E8167A1B3981E@PST.JCK.COM> <497D8756.5030306@pscs.co.uk> <6.2.5.6.2.20090126094552.02fdc008@resistor.net> <20090126181722.GN6078@jmac.e-dialog.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

At 10:17 26-01-2009, Jeff Macdonald wrote:
>Doesn't the above also allow the NAT IP as well?

Answering questions involving NAT or SLUT66 [1] is tricky as there 
may not be any right answer.

There isn't any mention in RFC 5321 about whether IPv4 addresses 
excludes the ranges of IP addresses defined in RFC 1918.  I cannot 
find a reason to add that to the specifications as SMTP is not 
restricted to the Internet or public routable IP addresses only.

Some people may argue that the SMTP client cannot be identified if it 
uses a RFC 1918 IP address in an address literal to communicate with 
a SMTP server on the Internet.  For operational reasons, it's better 
for such hosts to relay through a smarthost using SUBMIT.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/behave/current/msg05046.html