IETF Logo Mail Archive

Re: [BEHAVE] [v6ops] protocols without need for ALG ?

Joe Touch <touch@isi.edu> Fri, 31 July 2015 13:21 UTC

Return-Path: <touch@isi.edu>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D32671A87A1; Fri, 31 Jul 2015 06:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7YZFAor6TCeD; Fri, 31 Jul 2015 06:21:27 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3FFC1A87A9; Fri, 31 Jul 2015 06:21:27 -0700 (PDT)
Received: from [192.168.1.3] (pool-71-108-120-69.lsanca.dsl-w.verizon.net [71.108.120.69]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id t6VDL3Wi006080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 31 Jul 2015 06:21:05 -0700 (PDT)
References: <20150730205806.GI1667@cisco.com> <33A0B18B-5C9D-4DC3-9E0B-736D7ECA404F@delong.com> <alpine.DEB.2.02.1507310706240.11810@uplift.swm.pp.se> <CAO42Z2zH4A71B82TL3=tbagqXU1mbnt4eMDFGmuVa94gAj2-vA@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303EEFB81@UK30S005EXS06.EEAD.EEINT.CO.UK>
In-Reply-To: <6536E263028723489CCD5B6821D4B21303EEFB81@UK30S005EXS06.EEAD.EEINT.CO.UK>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="Apple-Mail-47C8F9D6-3F39-45B2-9176-A722B621781A"
Message-Id: <D99CCE3A-B396-4ED3-96BD-E9A9E92B2EDE@isi.edu>
X-Mailer: iPad Mail (12H143)
From: Joe Touch <touch@isi.edu>
Date: Fri, 31 Jul 2015 06:21:01 -0700
To: "Heatley, Nick" <nick.heatley@ee.co.uk>
X-MailScanner-ID: t6VDL3Wi006080
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/behave/Gm4_v7mPuy8abOJ3mFuzfj2tSqc>
Cc: v6ops list <v6ops@ietf.org>, "behave@ietf.org" <behave@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [BEHAVE] [v6ops] protocols without need for ALG ?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2015 13:21:30 -0000

TFTP servers are typically reached at UDP port 69.

It does not use ports or addresses in-band and thus should not need an ALG.

Joe

> On Jul 31, 2015, at 12:23 AM, Heatley, Nick <nick.heatley@ee.co.uk> wrote:
> 
> Same for me.
>  
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Mark Smith
> Sent: 31 July 2015 06:40
> To: Mikael Abrahamsson
> Cc: v6ops list; behave@ietf.org
> Subject: Re: [v6ops] protocols without need for ALG ?
>  
> 
> On 31 Jul 2015 3:11 pm, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:
> >
> > On Thu, 30 Jul 2015, Owen DeLong wrote:
> >
> >>>   SSH/SCP - OK
> >>>   syslog  - OK
> >>>   TFTP    - OK ?
> >>
> >>
> >> Should be OK, depending on which side is client. (client has to be the
> >> private address/translated side of the connection).
> >
> >
> > There are ALGs for TFTP from multiple vendors, and I seem to remember I had problem performing TFTP download from behind a NAT, but I could be mistaken. This should be investigated further.
> >
> 
> I'm pretty sure you'd need an ALG for TFTP over NAT, as the file transfer itself takes place over unspecified and unpredictable ports. This caused me some grief in the past when trying to have a TFTP file transfer hold up a dial on demand link.
> 
> Regards,
> Mark.
> 
> > -- 
> > Mikael Abrahamsson    email: swmike@swm.pp.se
> >
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> 
> NOTICE AND DISCLAIMER
> This e-mail (including any attachments) is intended for the above-named person(s).  If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose.  
>  
> We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.
> 
> EE Limited
> Registered in England and Wales
> Company Registered Number: 02382161
> Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW
> 
>  
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email