{"id":352221,"date":"2024-10-20T00:51:20","date_gmt":"2024-10-20T00:51:20","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-iso-iec-tr-29181-22014\/"},"modified":"2024-10-26T00:50:05","modified_gmt":"2024-10-26T00:50:05","slug":"bsi-pd-iso-iec-tr-29181-22014","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-iso-iec-tr-29181-22014\/","title":{"rendered":"BSI PD ISO\/IEC TR 29181-2:2014"},"content":{"rendered":"
This part of ISO\/IEC TR 29181 describes the general characteristics of Future Network naming and addressing schemes, including problem statements, requirements, design objectives, gap analysis, and development directions.<\/p>\n
Problem Statements: The characteristics and problems of existing NAS in existing network will be discussed.<\/p>\n<\/li>\n
Technical Challenges: A list of major technical challenges to assure that the FN-NAS will be able to provide solid technical support from the base level to meet the objectives of FN.<\/p>\n<\/li>\n
Requirements: The general characteristics of Future Network are discussed and their impact on NAS design.<\/p>\n<\/li>\n
Gap analysis: Examines the gap between existing network NAS and future network performance expectations.<\/p>\n<\/li>\n<\/ul>\n
In Annex A, FN-NAS Standardization Plan, design objectives, gap analysis, development guidance, chronological scenarios for future network naming, and addressing guidance are described in detail.<\/p>\n
Though this part of ISO\/IEC TR 29181 mainly presents a list of up-to-date surveyed problems, requirements, and plausible techniques for Future Network, it does not mean that all of those would be applied to a single Future Network in common, since the naming and addressing scheme can be applied to the various networks, such as global networks, local networks, access networks, mobile networks, etc. If a specific Future Network is designed and implemented, some appropriate parts of ISO\/IEC TR 29181 would be considered depending on its network usage and its characteristics.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
7<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1\tScope 2\tTerms and Definitions <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 3\tAbbreviations <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 4\tProblem statements 4.1\tNaming and Addressing in Network Operation 4.2\tNAS Types 4.2.1\tTelecom Network Naming and Addressing Schemes \u2014 addressing mode <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 4.2.2\tTelecom Network Naming and Addressing Schemes \u2014 naming mode 4.2.3\tComputer Network Naming and Addressing Schemes \u2014 dual mode <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 4.2.4\t.Computer Network Naming and Addressing Schemes \u2014 naming mode 4.2.5\tHybrid Network Naming and Addressing Schemes \u2014 Addressing mode <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 4.3\tProblems in Network Integration 4.4\tNAS and Network Performance <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 4.5\tTechnical Limitations of Existing Naming and Addressing System 4.5.1\tCentral Registration Authority 4.5.2\tAddress Space exhaustion 4.5.3\tName and Address Costs 4.5.4\tIdentifier-Locator Separation 4.5.5\tRouting Table 4.5.6\tVertical Addressing Structure 4.5.7\tDNS Translation 4.5.8\tData Encryption 4.5.9\tAddress Category <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 4.5.10\tPolicy 4.5.11\tNo Address in Native Language 4.5.12\tNo Decimal Naming System 4.5.13\tIPv6 Limitations 4.6\tFN-NAS Development Challenges 4.6.1\tScalability 4.6.2\tSecurity 4.6.3\tMobility: 4.6.4\tQuality of Service <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.6.5\tHeterogeneity 4.6.6\tRobustness: 4.6.7\tCustomizability 4.6.8\tEconomic incentives 5\tRequirements 5.1\tContent Description <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 5.2\tSystem Technical Requirements 5.2.1\tSystem Integrity Requirement 5.2.2\tIntersystem Coherence Requirement 5.2.3\tStructural Requirement <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5.2.4\tSpecific Technical Requirements <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5.2.5\tComplementary Technical Requirements 5.2.6\tExtension Technical Requirement <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.2.7\tEvaluation and Test Requirement 5.2.8\tInfrastructure Requirement <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | Annex\u00a0A \n(informative)<\/p>\n FN-NAS Standardization Plan <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Annex\u00a0B \n(informative)<\/p>\n Current Internet technology <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Annex\u00a0C \n(informative)<\/p>\n Current Internet Views <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Annex\u00a0D \n(informative)<\/p>\n Packet Transferring using Geographical addressing scheme <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Information technology. Future Network. Problem statement and requirements – Naming and addressing<\/b><\/p>\n |