summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc3167.txt
blob: 8a1e50ddd06f98c71ba5c707f3d8d565b7e730f2 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
Network Working Group                                           D. Meyer
Request for Comments: 3167                                        Sprint
Category: Informational                                       J. Scudder
                                                           Cisco Systems
                                                             August 2001


              Request to Move RFC 1745 to Historic Status

Status of this Memo

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

Copyright Notice

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

Abstract

   RFC 1745, "BGP4/IDRP for IP---OSPF Interaction", describes technology
   which was never deployed in the public internet.  This document
   requests that RFC 1745 be moved to Historic status.

1. Details

   During a review of internet standards relating to BGP, it became
   apparent that BGP/IDRP OSPF interaction, as described in RFC 1745,
   has never been deployed in the public internet, and would require
   significant implementation complexity.  Since this mechanism has
   never been in use in the public internet, it is proposed to
   reclassify it to Historic.

2. Security Considerations

   Moving RFC 1745 to Historic has no known effect on the security of
   the internet.

3. References

   [RFC1745]   Varadhan, K., Hares, S. and Y. Rekhter, "BGP4/IDRP for
               IP---OSPF Interaction", RFC 1745, December 1994.








Meyer & Scudder              Informational                      [Page 1]
^L
RFC 3167      Request to Move RFC 1745 to Historic Status    August 2001


4. Authors' Addresses

   David Meyer
   Sprint
   12502 Sunrise Valley Dr
   Reston VA,  20191
   MS VARESA-0105

   EMail: dmm@sprint.net


   John Scudder
   Cisco Systems, Inc.
   170 Tasman Drive
   San Jose, CA, 95134

   EMail: jgs@cisco.com


































Meyer & Scudder              Informational                      [Page 2]
^L
RFC 3167      Request to Move RFC 1745 to Historic Status    August 2001


Full Copyright Statement

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Meyer & Scudder              Informational                      [Page 3]
^L