RFC1435 IESG Advice from Experience with Path MTU Discovery

1435 IESG Advice from Experience with Path MTU Discovery. S. Knowles. March 1993. (Format: TXT=2708 bytes) (Status: INFORMATIONAL)

日本語訳
RFC一覧

参照

Network Working Group                                        S. Knowles
Request for Comments: 1435                                 ftp Software
                                                             March 1993


          IESG Advice from Experience with Path MTU Discovery

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard.  Distribution of this memo is
   unlimited.

Abstract

   In the course of reviewing the MTU Discovery protocol for possible
   elevation to Draft Standard, a specific operational problem was
   uncovered.  The problem results from the optional suppression of ICMP
   messages implemented in some routers.  This memo outlines a
   modification to this practice to allow the correct functioning of MTU
   Discovery.

Advice on the Deployment of Path MTU Discovery Protocol

   While reviewing the Path MTU Discovery Protocol for Draft Standard
   [RFC1191], the Internet Engineering Steering Group (IESG) became
   aware from the reports of various implementors that some vendors have
   added to their routers the ability to disable ICMP messages generated
   by the router.  This is to protect older BSD hosts, which would drop
   all connections to a host it found an ICMP message on any of the
   connections, even if it was a non-fatal ICMP message.  While this
   protects older BSD hosts, it causes MTU discovery to fail in a
   silent, hard to diagnose way.

   From the descriptions the IESG has obtained, adjusting the routers to
   continue to send ICMP message Type 3 code 4 (destination unreachable,
   don't fragment (DF) bit sent and fragmentation required) even when
   they have their "don't send ICMP messages" switch turned on would
   allow path MTU discovery to work but not effect older BSD hosts,
   since they never set the DF bit in their packets.

Author's Note

   This document was the result of an IESG meeting discussing MTU
   Discovery.  This author was chosen to write the document as the
   Internet Engineering Task Force (IETF) Internet Area Director.





Knowles                                                         [Page 1]

RFC 1435  IESG Advice from Experience with Path MTU Discovery March 1993


References

   [RFC1191] Mogul, J., and S. Deering, S., "Path MTU Discovery",
             RFC 1191, DECWRL, Stanford University, November 1990.

Security Considerations

   Security issues are not discussed in this memo.

Author's Address

   Stev Knowles
   ftp Software
   2 High Street
   North Andover, Ma, 01845

   EMail: stev@ftp.com


































一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

SIN関数 サイン

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る