[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Kerberos & PEM
See below for information on retrieving RFCs. In the same directory
as the RFCs themselves is a file called rfc-index.txt that has the
numbers and titles for all the rfcs. You can search through this for
kerberos or Privacy Enhanced Mail or firewalls or whatever. To get
RFC announcements, you should get on the ietf-announce mailing list.
Send a request to get on to ietf-announce-request@cnri.reston.va.us.
Donald
From: ERI <ERI@FRCU.EUN.EG>
To: ipsec@ans.net
X-Vms-To: IN%"ipsec@ans.net"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
>
>
>
>
>
>Dear sir,
>Would you please help me by sending the RFCs numbers that handles the
>following topics:
>
>1- RFCs pertaining to Kerberos
>2- RFCs about PEM
>
>If there is a new RFC will be issued. How can I know ?
>I knew that a RFC about firewells will issue within one month. Is it issued
>or not ? if issued what is the number?
>
>Thank you
>
>Waleed Hosny
>ERI@FRCU.EUN.EG
>112 Pyramids St. Giza - Egypt
>202 3830728
*------------------------------- REQUEST #1 ---------------------------------*
help: ways_to_get_rfcs
*------------------------------- RFC-INFO RESPONSE #1 -----------------------*
Where and how to get new RFCs
=============================
RFCs may be obtained via EMAIL or FTP from many RFC Repositories. The
Primary Repositories will have the RFC available when it is first
announced, as will many Secondary Repositories. Some Secondary
Repositories may take a few days to make available the most recent
RFCs.
Primary Repositories:
RFCs can be obtained via FTP from DS.INTERNIC.NET, FTP.NISC.SRI.COM,
NIS.NSF.NET, NISC.JVNC.NET, VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU,
SRC.DOC.IC.AC.UK, FTP.CONCERT.NET, or FTP.SESQUI.NET.
1. DS.INTERNIC.NET - InterNIC Directory and Database Services
RFC's may be obtained from DS.INTERNIC.NET via FTP, WAIS, and
electronic mail. Through FTP, RFC's are stored as rfc/rfcnnnn.txt or
rfc/rfcnnnn.ps where 'nnnn' is the RFC number. Login as "anonymous"
and provide your e-mail address as the password. Through WAIS, you
may use either your local WAIS client or telnet to DS.INTERNIC.NET and
login as "wais" (no password required) to access a WAIS client. Help
information and a tutorial for using WAIS are available online. The
WAIS database to search is "rfcs".
Directory and Database Services also provides a mail server
interface. Send a mail message to mailserv@ds.internic.net and
include any of the following commands in the message body:
document-by-name rfcnnnn where 'nnnn' is the RFC number
The text version is sent.
file /ftp/rfc/rfcnnnn.yyy where 'nnnn' is the RFC number.
and 'yyy' is 'txt' or 'ps'.
help to get information on how to use
the mailserver.
The InterNIC Directory and Database Services Collection of Resource
Listings, Internet Documents such as RFCs, FYIs, STDs, and Internet
Drafts, and Publically Accessible Databases are also now available via
Gopher. All our collections are waisindexed and can be searched from
the Gopher menu.
To access the InterNIC Gopher Servers, please connect to
"internic.net" port 70.
contact: admin@ds.internic.net
2. NIS.NSF.NET
To obtain RFCs from NIS.NSF.NET via FTP, login with username
"anonymous" and password "guest"; then connect to the directory of
RFCs with cd /internet/documents/rfc. The file name is of the form
rfcnnnn.txt (where "nnnn" refers to the RFC number).
For sites without FTP capability, electronic mail query is available
from NIS.NSF.NET. Address the request to NIS-INFO@NIS.NSF.NET and
leave the subject field of the message blank. The first text line of
the message must be "send rfcnnnn.txt" with nnnn the RFC number.
contact: rfc-mgr@merit.edu
3. NISC.JVNC.NET
RFCs can also be obtained via FTP from NISC.JVNC.NET, with the
pathname rfc/RFCnnnn.TXT.v (where "nnnn" refers to the number of the
RFC and "v" refers to the version number of the RFC).
JvNCnet also provides a mail service for those sites which cannot use
FTP. Address the request to SENDRFC@JVNC.NET and in the subject field
of the message indicate the RFC number, as in "Subject: RFCnnnn" where
nnnn is the RFC number. Please note that RFCs whose number are less
than 1000 need not place a "0". (For example, RFC932 is fine.) No
text in the body of the message is needed.
contact: Becker@NISC.JVNC.NET
4. VENERA.ISI.EDU
RFCs can be obtained via FTP from VENERA.ISI.EDU, with the pathname
in-notes/rfcnnnn.txt (where "nnnn" refers to the number of the RFC).
Login with FTP username "anonymous" and password "guest".
RFCs can also be obtained via electronic mail from VENERA.ISI.EDU by
using the RFC-INFO service. Address the request to "rfc-info@isi.edu"
with a message body of:
Retrieve: RFC
Doc-ID: RFCnnnn
(Where "nnnn" refers to the number of the RFC (always use 4 digits -
the DOC-ID of RFC-822 is "RFC0822")). The RFC-INFO@ISI.EDU server
provides other ways of selecting RFCs based on keywords and such; for
more information send a message to "rfc-info@isi.edu" with the message
body "help: help".
contact: RFC-Manager@ISI.EDU
5. WUARCHIVE.WUSTL.EDU
RFCs can also be obtained via FTP from WUARCHIVE.WUSTL.EDU, with the
pathname info/rfc/rfcnnnn.txt.Z (where "nnnn" refers to the number of the
RFC and "Z" indicates that the document is in compressed form).
At WUARCHIVE.WUSTL.EDU the RFCs are in an "archive" file system and
various archives can be mounted as part of an NFS file system.
Please contact Chris Myers (chris@wugate.wustl.edu) if you want to
mount this file system in your NFS.
contact: chris@wugate.wustl.edu
6. SRC.DOC.IC.AC.UK
RFCs can be obtained via FTP from SRC.DOC.IC.AC.UK with the pathname
rfc/rfcnnnn.txt.Z or rfc/rfcnnnn.ps.Z (where "nnnn" refers to the
number of the RFC). Login with FTP username "anonymous" and password
"your-email-address". To obtain the RFC Index, use the pathname
rfc/rfc-index.txt.Z. (The trailing .Z indicates that the document is
in compressed form.)
SRC.DOC.IC.AC.UK also provides an automatic mail service for those
sites in the UK which cannot use FTP. Address the request to
info-server@doc.ic.ac.uk with a Subject: line of "wanted" and a
message body of:
request sources
topic path rfc/rfcnnnn.txt.Z
request end
(Where "nnnn" refers to the number of the RFC.) Multiple requests may
be included in the same message by giving multiple "topic path"
commands on separate lines. To request the RFC Index, the command
should read: topic path rfc/rfc-index.txt.Z
The archive is also available using NIFTP and the ISO FTAM system.
contact: ukuug-soft@doc.ic.ac.uk
7. FTP.CONCERT.NET
To obtain RFCs from FTP.CONCERT.NET via FTP, login with username
"anonymous" and your internet e-mail address as password. The RFCs
can be found in the directory /rfc, with file names of the form:
rfcNNNN.txt or rfcNNNN.ps where NNNN refers to the RFC number.
This repository is also accessible via WAIS and the Internet Gopher.
contact: rfc-mgr@concert.net
8. FTP.SESQUI.NET
RFCs can be obtained via FTP from FTP.SESQUI.NET, with the pathname
pub/rfc/rfcnnnn.xxx (where "nnnn" refers to the number of the RFC and
xxx indicates the document form, txt for ASCII and ps for Postscript).
At FTP.SESQUI.NET the RFCs are in an "archive" file system and
various archives can be mounted as part of an NFS file system.
Please contact RFC-maintainer (rfc-maint@sesqui.net) if you want to
mount this file system in your NFS.
contact: rfc-maint@sesqui.net
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Secondary Repositories:
Sweden
------
Host: sunic.sunet.se
Directory: rfc
Host: chalmers.se
Directory: rfc
Germany
-------
Site: University of Dortmund
Host: walhalla.informatik.uni-dortmund.de
Directory: pub/documentation/rfc
Notes: RFCs in compressed format
France
------
Site: Institut National de la Recherche en Informatique
et Automatique (INRIA)
Address: info-server@inria.fr
Notes: RFCs are available via email to the above
address. Info Server manager is Mireille
Yamajako (yamajako@inria.fr).
Netherlands
-----------
Site: EUnet
Host: mcsun.eu.net
Directory: rfc
Notes: RFCs in compressed format.
Finland
-------
Site: FUNET
Host: funet.fi
Directory: rfc
Notes: RFCs in compressed format. Also provides
email access by sending mail to
archive-server@funet.fi.
Norway
------
Host: ugle.unit.no
Directory: pub/rfc
Denmark
-------
Site: University of Copenhagen
Host: ftp.diku.dk (freja.diku.dk)
Directory: rfc
Australia and Pacific Rim
-------------------------
Site: munnari
Contact: Robert Elz <kre@cs.mu.OZ.AU>
Host: munnari.oz.au
Directory: rfc
rfc's in compressed format rfcNNNN.Z
postscript rfc's rfcNNNN.ps.Z
United States
-------------
Site: cerfnet
Contact: help@cerf.net
Host: nic.cerf.net
Directory: netinfo/rfc
Site: NASA NAIC
Contact: rfc-updates@naic.nasa.gov
Host: naic.nasa.gov
Directory: files/rfc
Site: NIC.DDN.MIL (DOD users only)
Contact: NIC@nic.ddn.mil
Host: NIC.DDN.MIL
Directory: rfc/rfcnnnn.txt
Note: DOD users only may obtain RFC's via FTP
from NIC.DDN.MIL. Internet users should NOT
use this source due to inadequate connectivity.
Site: uunet
Contact: James Revell <revell@uunet.uu.net>
Host: ftp.uu.net
Directory: inet/rfc
UUNET Archive
-------------
UUNET archive, which includes the RFC's, various IETF documents,
and other information regarding the internet, is available to the
public via anonymous ftp (to ftp.uu.net) and anonymous uucp, and
will be available via an anonymous kermit server soon. Get the
file /archive/inet/ls-lR.Z for a listing of these documents.
Any site in the US running UUCP may call +1 900 GOT SRCS and use
the login "uucp". There is no password. The phone company will
bill you at $0.50 per minute for the call. The 900 number only
works from within the US.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Requests for special distribution of RFCs should be addressed to
either the author of the RFC in question, to NIC@INTERNIC.NET.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Requests to be added to or deleted from the RFC distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.
Changes to this file "rfc-retrieval.txt" should be sent to
RFC-MANAGER@ISI.EDU.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
References: