Re: IPv4 Outage Planned for IETF 71 Plenary
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IPv4 Outage Planned for IETF 71 Plenary
- To: <alh-ietf at tndh.net>
- Subject: Re: IPv4 Outage Planned for IETF 71 Plenary
- From: Sam Hartman <hartmans-ietf at mit.edu>
- Date: Wed, 19 Dec 2007 16:28:38 -0500
- Cc: ietf at ietf.org, iaoc at ietf.org, 'Pete Resnick' <presnick at qualcomm.com>, 'IETF Chair' <chair at ietf.org>, dcrocker at bbiw.net, 'John C Klensin' <john-ietf at jck.com>, iesg at ietf.org
- In-reply-to: <083201c84283$9e4489e0$dacd9da0$@net> (Tony Hain's message of "Wed, 19 Dec 2007 13:10:43 -0800")
- List-help: <mailto:ietf-request@ietf.org?subject=help>
- List-id: IETF-Discussion <ietf.ietf.org>
- List-post: <mailto:ietf@ietf.org>
- List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
- References: <E1J3IFS-0002yV-CG@ietf.org> <200712142154.lBELs1ne090300@drugs.dv.isc.org> <200712181644.lBIGisBx090029@romeo.rtfm.com> <476800BC.5030504@dcrocker.net> <38033976C354EAB237181075@[192.168.101.1]> <p06250103c38dc78214d8@[74.134.5.163]> <080c01c84276$ec9a79e0$c5cf6da0$@net> <tsl8x3qphdd.fsf@mit.edu> <083201c84283$9e4489e0$dacd9da0$@net>
- User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
>>>>> "Tony" == Tony Hain <alh-ietf at tndh.net> writes:
Tony> Sam, While I understand the virtue in behave-compatible
Tony> nats, how realistic is it to believe that any service
Tony> provider is going to allow a consumer to directly signal
Tony> their infrastructure?
The behave documents I've read don't talk about signaling a NAT. Are
we talking about the same working group?
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions
of the senders and do not imply endorsement by the IETF.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.
