Selasa, 02 April 2013

Internet Standard Document: X800 vs RFC 2828

Hi there.. This is my first time, i post something in my blog..
Well, actually that, this is my College homework.. Even, honestly, really confused about this homework.. @.@

First of all, i am going to write about "Internet Standard":

In computer network engineering, an Internet Standard (abbreviated as "STD") is a normative specification of a technology or methodology applicable to the Internet. Internet Standards are created and published by the Internet Engineering Task Force (IETF).

An Internet Standard is characterized by a high degree of technical maturity and by a generally held belief that the specified protocol or service provides significant benefit to the Internet community. Generally Internet Standards cover interoperability of systems on the Internet through defining protocols, message formats, schemas, and languages. The most fundamental of the Internet Standards are the ones defining the Internet Protocol.

An Internet Standard ensures that hardware and software produced by different vendors can work together. Having a standard makes it much easier to develop software and hardware that link different networks because software and hardware can be developed one layer at a time. Normally, the standards used in data communication are called protocols.

Next, i am going to write about the "Standard Documents And Series" .. In here, there are 2 series what i am going to write ..
The First one is ITU-T: X Series ====> "X.800"
and, the second one is RFC ====> "RFC 2828"


1. X.800
X.800 defines the general security-related architectural elements which can be applied appropriately in the circumstances for which protection of communication between open systems is required. It establishes, within the framework of the Reference Model (Read:"X.200"), guidelines and constraints to improve existing Recommendations (Read:"X.800") or to develop new Recommendations in the context of OSI in order to allow secure communications and thus provide a consistent-approach to security in OSI.

This Recommendation:
a. Provides a general description of security services and related mechanisms, which may be provided by the Reference Model; and
b. Defines the positions within the Reference Model where the services and mechanims may be provided.

So,
This Recommendation extends the field of application of Recommendation X.200, to cover secure communications between open systems.


2. RFC 2828
a Request for Comments (RFC) is a memorandum published by the Internet Engineering Task Force (IETF) describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems.

RFC 2828 defines the security service is a processing or communication service that is provided by a system to give a specific kind of protection to system resources; security services implement security policies and are implemented by security mechanisms.

Each RFC is static; if the document is changed, it is submitted again and assigned a new RFC number. If an RFC becomes an Internet Standard (STD), it is assigned an STD number but retains its RFC number. When an Internet Standard is updated, its number stays the same and it simply refers to a different RFC or set of RFCs. A given Internet Standard, STD n, may be RFCs x and y at a given time, but later the same standard may be updated to be RFC z instead.

 For example, in 2007 RFC 3007 was an Internet Standard—STD 1—and in May 2008 it was replaced with RFC 5000, so RFC 3700 changed to Historic status, and now STD 1 is RFC 5000. When STD 1 is updated again, it will simply refer to a newer RFC, but it will still be STD 1. Note that not all RFCs are standards-track documents, but all Internet Standards and other standards-track documents are RFCs.


I think, that's all for today.. i will write about it again whenever i have any information about it again.
Sorry, if my writing is a bit mess, because this is my first time write something into my blog..
Thank you :)

Tidak ada komentar:

Posting Komentar