Found 1 record.

Status: Reported (1)

RFC 1403, "BGP OSPF Interaction", January 1993

Errata ID: 6898
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Jesus Manuel Alvarado
Date Reported: 2022-03-28

Section 1403 says:

Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-03-31
Held for Document Update by: Magnus Westerlund

Section 3.2,last par says:

   A variety of current peer-to-peer applications implement this
   technique.  Its main limitation, of course, is that it only works so
   long as only one of the communicating peers is behind a NAT device.
|  If the NAT device is EIM-NAT, the public client can contact external
|  server S to determine the specific public endpoint from which to
|  expect Client-A-originated connection and allow connections from just
|  those endpoints.  If the NAT device is EIM-NAT, the public client can
   contact the external server S to determine the specific public
   endpoint from which to expect connections originated by client A, and
   allow connections from just that endpoint.  If the NAT device is not
   EIM-NAT, the public client cannot know the specific public endpoint
   from which to expect connections originated by client A.  In the
   increasingly common case where both peers can be behind NATs, the
   Connection Reversal method fails.  [...]
It should say:

   A variety of current peer-to-peer applications implement this
   technique.  Its main limitation, of course, is that it only works so
   long as only one of the communicating peers is behind a NAT device.
   If the NAT device is EIM-NAT, the public client can contact the
   external server S to determine the specific public endpoint from
   which to expect connections originated by client A, and allow
   connections from just that endpoint.  If the NAT device is not
   EIM-NAT, the public client cannot know the specific public endpoint
   from which to expect connections originated by client A.  In the
   increasingly common case where both peers can be behind NATs, the
   Connection Reversal method fails.  [...]
Notes:

Location is mid-page 11.

Rationale and background:

The reporter once had suggested replacement text to improve the
readability of the third and fourth sentence in this paragraph.
These LC comments have been accepted, but inadvertently, the
third original sentence has been left in the text, followed
by its intended replacement.

Note that the similar replacement of the next sentence
("If the NAT device is not ...") has been performed properly.

The above correction removes the original, less legible draft
version of the other sentence.

It should say:

The problem is it wasn’t a old version that hit something alpha’s won’t talk about and more I held back from doing more of those tests google chrome hmmm.2012

Notes:

Yahoo pornhub chrome any ideas why I said federal contract different I wouldn’t sub contract one person because in the being no one would of seen the smart world coming in…! Sad

Report New Errata