پایان نامه کامپیوتر
انجام پایان نامه ارشد کامپیوتر
Internet Protocol version 6 (IPv6) is a network layer protocol for packet-switched internetworks. It is designated as the successor of IPv4, the current version of the Internet Protocol, for general use on the Internet.
The main improvement brought by IPv6 is the increase in the number of addresses available for networked devices, allowing, for example, each mobile phone and mobile electronic device to have its own address. IPv4 supports 232 (about 4.3 billion) addresses, which is inadequate for giving even one address to every living person, let alone supporting embedded and portable devices. IPv6, however, supports 2128 (about 340 billion billion billion billion) addresses, or approximately 5×1028 addresses for each of the roughly 6.5 billion people alive today. With such a large address space available, IPv6 nodes can have as many universally scoped addresses as they need, and network address translation is not required.
By the early 1990s, it was clear that the change to a classless network introduced a decade earlier was not enough to prevent the IPv4 address exhaustion and that further changes to IPv4 were needed. By the winter of 1992, several proposed systems were being circulated and by the fall of 1993, the IETF announced a call for white papers (RFC 1550) and the creation of the "IPng Area" of working groups.
IPng was adopted by the Internet Engineering Task Force on July 25, 1994 with the formation of several "IP Next Generation" (IPng) working groups. By 1996, a series of RFCs were released defining IPv6, starting with RFC 2460. (Incidentally, IPv5 was not a successor to IPv4, but an experimental flow-oriented streaming protocol intended to support video and audio.)
It is expected that IPv4 will be supported alongside IPv6 for the foreseeable future. However, IPv4-only clients/servers will not be able to communicate directly with IPv6 clients/servers, and will require service-specific intermediate servers or NAT-PT protocol-translation servers. Free Ipv4 adresseses will exhaust around 2010, which is within the depreciation time of equipment currently being acquired.
Features of IPv6
To a great extent, IPv6 is a conservative extension of IPv4. Most transport- and application-layer protocols need little or no change to work over IPv6; exceptions are applications protocols that embed network-layer addresses (such as FTP or NTPv3).
Applications, however, usually need small changes and a recompile in order to run over IPv6.
Larger address space
The main feature of IPv6 that is driving adoption today is the larger address space: addresses in IPv6 are 128 bits long versus 32 bits in IPv4.
The larger address space avoids the potential exhaustion of the IPv4 address space without the need for network address translation and other devices that break the end-to-end nature of Internet traffic. It also makes administration of medium and large networks simpler, by avoiding the need for complex subnetting schemes. Subnetting will, ideally, revert to its purpose of logical segmentation of an IP network for optimal routing and access.
The drawback of the large address size is that IPv6 carries some bandwidth overhead over IPv4, which may hurt regions where bandwidth is limited (header compression can sometimes be used to alleviate this problem). The address size also lacks the immediate memorability of the more familiar, shorter IPv4 address.
Stateless autoconfiguration of hosts
IPv6 hosts can be configured automatically when connected to a routed IPv6 network. When first connected to a network, a host sends a link-local multicast (broadcast) request for its configuration parameters; if configured suitably, routers respond to such a request with a router advertisement packet that contains network-layer configuration parameters.
If IPv6 autoconfiguration is not suitable, a host can use stateful autoconfiguration (DHCPv6) or be configured manually.
Stateless autoconfiguration is only suitable for hosts: routers must be configured manually or by other means.
Multicast is part of the base protocol suite in IPv6. This is in opposition to IPv4, where multicast is optional.
Most environments do not currently have their network infrastructures configured to route multicast; that is — the link-scoped aspect of multicast will work but the site-scope, organization-scope and global-scope multicast will not be routed.
IPv6 does not have a link-local broadcast facility; the same effect can be achieved by multicasting to the all-hosts group (FF02::1).
The m6bone is catering for deployment of a global IPv6 Multicast network.
In IPv4, packets are limited to 64 KiB of payload. When used between capable communication partners and on communication links with a maximum transmission unit larger than 65,576 octets, IPv6 has optional support for packets over this limit, referred to as jumbograms which can be as large as 4 GiB. The use of jumbograms may improve performance over high-MTU networks.
IPsec, the protocol for IP network-layer encryption and authentication, is an integral part of the base protocol suite in IPv6; this is unlike IPv4, where it is optional (but usually implemented). IPsec, however, is not widely deployed except for securing traffic between IPv6 BGP routers.
Unlike mobile IPv4, Mobile IPv6 (MIPv6) avoids triangular routing and is therefore as efficient as normal IPv6. This advantage is mostly hypothetical, as neither MIP nor MIPv6 are widely deployed today.
As of December 2005, IPv6 accounts for a tiny percentage of the live addresses in the publicly-accessible Internet, which is still dominated by IPv4. The adoption of IPv6 has been slowed by the introduction of classless inter-domain routing (CIDR) and network address translation (NAT), each of which has partially alleviated the impact of address space exhaustion. Estimates as to when the pool of available IPv4 addresses will be exhausted vary — in 2003, Paul Wilson (director of APNIC) stated that, based on then-current rates of deployment, the available space would last until 2023, while in September 2005 a report by Cisco Systems that the pool of available addresses would be exhausted in as little as 4–5 years. As of November 2006, a regularly updated report projected that the IANA pool of unallocated addresses would be exhausted in May 2011, with the various Regional Internet Registries using up their allocations from IANA in August 2012. This report also argues that, if assigned but unused addresses were reclaimed and used to meet continuing demand, allocation of IPv4 addresses could continue until 2024. The U.S. Government has specified that the network backbones of all federal agencies must deploy IPv6 by 2008. But there are two specific challenges to this requirement. 1) There is no special federal funding available for IPv6 transitions. Thus agencies are expected to make the migration via their ongoing equipment purchases and network updates. Most agencies now have their transition plan in place, but surveys have noted that many are lagging when it comes to making that transition a reality. . 2) Agency IT budgets are tight at the moment, especially since the current 2007 IT Budget has been stalled, thanks to the Continuing Resolution.
Meanwhile China is planning to get a head start implementing IPv6 with their 5 year plan for the China Next Generation Internet.
With the notable exceptions of stateless autoconfiguration, more flexible addressing and Secure Neighbor Discovery (SEND), many of the features of IPv6 have been ported to IPv4 in a more or less elegant manner. Thus IPv6 deployment is primarily driven by address space exhaustion.
The primary change from IPv4 to IPv6 is the length of network addresses. IPv6 addresses are 128 bits long (as defined by RFC 4291), whereas IPv4 addresses are 32 bits; where the IPv4 address space contains roughly 4 billion addresses, IPv6 has enough room for 3.4×1038 unique addresses.
IPv6 addresses are typically composed of two logical parts: a 64-bit (sub-)network prefix, and a 64-bit host part, which is either automatically generated from the interface's MAC address or assigned sequentially. Because the globally unique MAC addresses offer an opportunity to track user equipment, and so users, across time and IPv6 address changes, RFC 3041 was developed to reduce the prospect of user identity being permanently tied to an IPv6 address, thus restoring some of the possibilities of anonymity existing at IPv4. RFC 3041 specifies a mechanism by which time-varying random bit strings can be used as interface circuit identifiers, replacing unchanging and traceable MAC addresses.
IPv6 addresses are normally written as eight groups of four hexadecimal digits. For example, 2001:0db8:85a3:08d3:1319:8a2e:0370:7334 is a valid IPv6 address.
If a four-digit group is 0000, the zeros may be omitted and replaced with two colons(::). For example, 2001:0db8:0000:0000:0000:0000:1428:57ab can be shortened as 2001:0db8::1428:57ab. Following this rule, any number of consecutive 0000 groups may be reduced to two colons, as long as there is only one double colon used in an address. Leading zeros in a group can also be omitted. Thus, the addresses below are all valid and equivalent:
Having more than one double-colon abbreviation in an address is invalid, as it would make the notation ambiguous.
A sequence of 4 bytes at the end of an IPv6 address can also be written in decimal, using dots as separators. This notation is often used with compatibility addresses (see below). Thus, ::ffff:188.8.131.52 is the same address as ::ffff:0102:0304, and ::ffff:184.108.40.206 is the same address as ::ffff:0f10:121f.
Additional information can be found in RFC 4291 - IP Version 6 Addressing Architecture.
Literal IPv6 Addresses in URLs
In a URL the IPv6-Address is enclosed in brackets. Example:
This notation allows parsing a URL without confusing the IPv6 address and port number:
Additional information can be found in "RFC 2732 - Format for Literal IPv6 Addresses in URL's" and "RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax"
IPv6 networks are written using CIDR notation.
An IPv6 network (or subnet) is a contiguous group of IPv6 addresses the size of which must be a power of two; the initial bits of addresses, which are identical for all hosts in the network, are called the network's prefix.
• A network is denoted by the first address in the network and the size in bits of the prefix (in decimal), separated with a slash. For example, 2001:0db8:1234::/48 stands for the network with addresses 2001:0db8:1234:0000:0000:0000:0000:0000 through 2001:0db8:1234:FFFF:FFFF:FFFF:FFFF:FFFF
Because a single host can be seen as a network with a 128-bit prefix, you will sometimes see host addresses written followed with /128.
Kinds of IPv6 addresses
IPv6 addresses are divided into 3 categories  :
• Unicast Addresses
• Multicast Addresses
• Anycast Addresses
A Unicast address defines a single interface. It identifies a single network interface A packet sent to a unicast address is delivered to that specific computer.
Multicast addresses are used to define a set of interfaces that typically belong to different nodes instead of just one. When a packet is sent to a multicast address, the protocol delivers the packet to all interfaces identified by that address. Multicast addresses begin with the prefix FF00::/8, and their second octet identifies the addresses scope, i.e. the range over which the multicast address is propagated. Commonly used scopes include link-local (2), site-local (5) and global (E).
Anycast addresses, are also assigned to more than one interface, belonging to different nodes. However, a packet sent to an anycast address is delivered to just one of the member interfaces, typically the “nearest” according to the routing protocol’s idea of distance. Anycast addresses cannot be identified easily: they have the structure of normal unicast addresses, and differ only by being injected into the routing protocol at multiple points in the network.
There are a number of addresses with special meaning in IPv6:
• ::/128 — the address with all zeros is an unspecified address, and is to be used only in software.
• ::1/128 — the loopback address is a localhost address. If an application in a host sends packets to this address, the IPv6 stack will loop these packets back to the same host (corresponding to 127.0.0.1 in IPv4).
• ::/96 — the zero prefix was used for IPv4-compatible addresses; it is now obsolete.
• ::ffff:0:0/96 — this prefix is used for IPv4 mapped addresses (see Transition mechanisms below).
• 2001:db8::/32 — this prefix is used in documentation (RFC 3849). Anywhere where an example IPv6 address is given, addresses from this prefix should be used.
• fc00::/7 — Unique Local Addresses (ULA) are routable only within a set of cooperating sites. They were defined in RFC 4193 as a replacement for site-local addresses (see below). The addresses include a 40-bit pseudorandom number that minimizes the risk of conflicts if sites merge or packets somehow leak out. This address space is split into two parts:
o fc00::/8 — - ULA Central, currently not used as the draft is expired.
o fd00::/8 — - ULA, as per RFC 4193, Generator and unofficial registry.
• fe80::/64 — The link-local prefix specifies that the address only is valid in the local physical link. This is analogous to the Autoconfiguration IP address 169.254.x.x in IPv4.
• fec0::/10 — The site-local prefix specifies that the address is valid only inside the local organisation. Its use has been deprecated in September 2004 by RFC 3879 and systems must not support this special type of address.
• ff00::/8 — The multicast prefix is used for multicast addresses as defined by in "IP Version 6 Addressing Architecture" (RFC 4291).
There are no address ranges reserved for broadcast in IPv6 — applications use multicast to the all-hosts group instead. IANA maintains the official list of the IPv6 address space. Global unicast assignments can be found at the various RIR's or at the GRH DFP pages.
The structure of an IPv6 packet header.
The IPv6 packet is composed of two main parts: the header and the payload.
The header is in the first 40 octets/bytes of the packet and contains both source and destination addresses (128 bits each), as well as the version (4-bit IP version), traffic class (8 bits, Packet Priority), flow label (20 bits, QoS management), payload length in bytes (16 bits), next header (8 bits), and hop limit (8 bits, time to live). The payload can be up to 64KiB in size in standard mode, or larger with a "jumbo payload" option.
Fragmentation is handled only in the sending host in IPv6: routers never fragment a packet, and hosts are expected to use PMTU discovery.
The protocol field of IPv4 is replaced with a Next Header field. This field usually specifies the transport layer protocol used by a packet's payload.
In the presence of options, however, the Next Header field specifies the presence of an extra options header, which then follows the IPv6 header; the payload's protocol itself is specified in a field of the options header. This insertion of an extra header to carry options is analogous to the handling of AH and ESP in IPsec for both IPv4 and IPv6.
IPv6 and the Domain Name System
IPv6 addresses are represented in the Domain Name System by AAAA records (so-called quad-A records) for forward lookups; reverse lookups take place under ip6.arpa (previously ip6.int), where address space is delegated on nibble boundaries. This scheme, which is a straightforward adaptation of the familiar A record and in-addr.arpa schemes, is defined in RFC 3596.
The AAAA scheme was one of two proposals at the time the IPv6 architecture was being designed. The other proposal, designed to facilitate network renumbering, would have had A6 records for the forward lookup and a number of other innovations such as bit-string labels and DNAME records. It is defined in the experimental RFC 2874 and its references (with further discussion of the pros and cons of both schemes in RFC 3364).
RFC 3484 specifies how applications should select an IPv6 or IPv4 address for use, including addresses retrieved from DNS.
به اجرا درآوردن مدیریت کیفیت فراگیر سبب بالارفتن سطح کارایی سازمانهای تولیدی و خدماتی می شود و استفاده از این روش مدیریت، موجب افزایش توجه گروه های ذینفع به عملکرد سازمان می شود و این توجه زمینه ساز بروز فرصتهای طلایی برای حضوری موفق در عرصه رقابتها خواهد بود. لذا اهمیت این بخش از تحقیق در چرائی پرداختن به پژوهش در چارچوب اهداف آن با تعیین درست مسئله لازم می باشد، تعیین این هدف مستلزم شناخت سیر اندیشه مدیریت کیفیت می باشد که در این فصل به تفصیل به آن پرداخته شده است.
تحقیق و پژوهشی که به صورت علمی انجام پذیرد بر پایه ها، ارکان و نتایج مطالعات و تحقیقات پیشین استوار است. در این تحقیق سعی شده تا مرتبط ترین دستاوردهای تحقیقات پژوهشگران گذشته را مورد شناسایی قرار داده و دریابیم که دیگران تا چه اندازه مساله موردنظر را بررسی کرده اند و به آن نزدیک شده اند به عبارت دیگر چه ابعاد از مساله تحقیق بررسی شده و چه ابعادی بررسی نشده است.
1-2: بخش اول: مدیریت کیفیت فراگیر
1-1-2 مفهوم کیفیت
تعاریف بسیار زیادی از واژه کیفیت شده است اما وجه مشترک این تعاریف سازگاری و تطابق کالا یا خدمت با نیازها و انتظارات مشتری است و مشتری هم کسی است که کالا یا خدمتی را به طور کامل و یا حتی به صورت نیمه تمام تحویل می گیرد. بنابراین مشتری ها هم در داخل و هم خارج از سازمان هستند، لذا می توان گفت که تنوع مشتری خارجی، متناسب با انواع کالاها و با خدمات قابل ارائه است ولی تعداد مشتریان داخل به مراتب زیادتر است زیرا در یک سازمان ساده هر بخش بعنوان داده بخش دیگر محسوب می شود و یک مشتری درنظر گرفته می شود.
با عنایت به کثرت مشتری در مقابل تنوع کالاهای تولیدی و خدماتی قابل ارائه تعاریف زیر مورد استفاده است:
1-1) استاندارد ISO کیفیت را این گونه تعریف می کند: کیفیت یک محصول یا خدمت، میزان تطبیق آن با ارضا نیاز مشتری با اساس رضایت است.]1[
2-1) در دهه 1950 ادوارد دمینگ و فیکن باوم مفهوم کیفیت را اینگونه تعریف بیان کردند:
کیفیت مفهوم وسیعی است که تمام بخشهای مختلف سازمان نسبت به آن متعهد هستند و هدف آن افزایش کارایی کل مجموعه است بطوری که مانع پدید آمدن عوامل مخل کیفیت شود. هدف نهایی آن مطابقت کامل با مشخصات موردنیاز مشتری با حداقل هزینه برای سازمان است که منجر به افزایش قابلیت رقابت می شود]2[.
انجام پایان نامه
انجام پایان نامه کامپیوتر، انجام پایان نامه ارشد کامپیوتر، انجام پایان نامه، پایان نامه
برای دیدن ادامه مطلب از لینک زیر استفاده نمایید