InterPlanetary Networking Special Interest Group (IPNSIG) Rotating Header Image

2. IPN Internet Engineering

FACT SHEET:  IPN INTERNET ENGINEERING FRAMEWORK

The purpose of this fact sheet is to introduce the IPN Internet Engineering Framework, including goals, projects, and proposed constituent elements. This program is part of the InterPlanetary Network Special Interest Group (IPNSIG), an Internet Society (ISOC) chapter, operated and supported by the San Francisco Bay Internet Society (SFBayISOC).

 The IPN Internet Engineering Framework is an IPN Academic Relations initiative, designed to promote collaboration among the IPNSIG, academic institutions, and partners. This is accomplished via Research and Development projects in Internet Engineering that extend IPN capabilities. All projects are administered in accordance with the IPN Academic Relations processes, policies, and standards.

 

GOALS

  1. ALIGNMENT with the IPN DELAY and DISRUPTION TOLERANT NETWORK: The IPN DTN Architecture is the primary project of the IPN Integrated Architecture, and provides analysis, recommendations, and the architecture for the use of DTN as the foundational Internet Protocol of the IPN Architecture.

  2. CONTINUE and CONVERGE EXISTING ACTIVITIES: Leverage existing work-in-progress to continue building the foundation of the IPN Internet Engineering Framework, including converging projects, activities, and resources where appropriate.

  3. EXPAND EXISTING and INITIATE NEW ACTIVITIES: Expand existing projects and/or initiate new projects, in response to IPN activity and funding allocated to the Internet Engineering Framework.

  4. ESTABLISH, MAINTAIN, and EVOLVE the IPN INTERNET ENGINEERING INTEGRATED ARCHITECTURE: Develop and maintain the IPN Internet Engineering Integrated Architecture, including defining appropriate constituent elements, in compliance with the IPN Integrated Architecture processes, policies, and standards.
  5. ALIGN with the IPN INTEGRATED FRAMEWORK: Integrate the IPN Internet Engineering Framework with the IPN Integrated Framework, which includes the IPN Astronautical Engineering Framework, and the IPN Cognitive Sciences Framework.
  6. ENGAGE ISOC MEMBERS: Invite global ISOC chapter members to participate on IPN Internet Engineering projects, specific to their interests.
  7. ENGAGE CAMPUS PARTY MEMBERS: Partner with Campus Party to develop IPN Internet Engineering projects specific to each Campus Party event’s focus.
  8. ENGAGE ACADEMIC MEMBERS: Partner with academia on IPN Internet Engineering projects specific to their research strengths and interests.
  9. SHOWCASE PROJECTS at EVENTS: Present IPN Internet Engineering Framework information, and showcase projects, including demos, during ISOC, Campus Party, and academic events.

 

PROJECTS

Existing and proposed activities and projects of the IPN Internet Engineering Framework are selected in accordance with the IPN Integrated Framework Project Selection Criteria, (see Reference List below),  which is based on each proposed project’s contribution to the IPN. The IPN Integrated Framework  Project Registry, provides the portfolio of existing projects, as well as the process to submit proposed projects for review and approval. ISOC members, Campus Party members, and academic research centers are invited to participate in existing projects. or submit new proposals, according to their expertise, strengths, and interests.

 

CONSTITUENT ELEMENTS

Six elements constitute the IPN Internet Engineering Architecture, in accordance with short-term and long-term goals and capabilities of the IPN Integrated Architecture. These are listed below:

  1. IPN Internet Engineering Requirements
  2. Application Architecture
  3. Data Architecture
  4. Infrastructure Architecture
  5. Security Architecture
  6. Integration with the IPN Integrated Architecture

These six elements have been selected based on the need for an application, data, infrastructure, and security architecture running the IPN-compliant Internet protocol, specifically the DTN protocol. Additional elements may be added to the IPN Internet Engineering Architecture, in alignment with IPN’s future goals and capabilities. A brief description of each of the 6 elements listed above is provided below.

 IPN INTERNET ENGINEERING REQUIREMENTS:  The IPN Internet Engineering User Requirements provides a blueprint that specifies the use cases, functional requirements, capabilities delivered as services, and the service interfaces that enable integration in accordance with the IPN Integrated Architecture standards.

IPN INTERNET ENGINEERING APPLICATION ARCHITECTURE:  The IPN Internet Engineering Application Architecture provides the list of applications and their functionality and capabilities based on IPN use case requirements, and specifies modular application interfaces that enable integration in accordance with the IPN Integrated Architecture standards.

IPN INTERNET ENGINEERING DATA ARCHITECTURE:  The IPN Internet Engineering Data Architecture provides the data structures used by the applications specified by the IPN Internet Engineering Application Architecture, and how data is processed, stored, transported, and utilized by the applications.

IPN INTERNET ENGINEERING INFRASTRUCTURE ARCHITECTURE:  The IPN Internet Engineering Infrastructure Architecture provides the infrastructure hardware, infrastructure software, and infrastructure networks that enable the development, testing, deployment, monitoring, and controlling of IPN applications.

IPN INTERNET ENGINEERING SECURITY ARCHITECTURE:  The IPN Internet Engineering Security Architecture defines the IPN operational environments and risks, and provides the necessary elements to maintain the availability of all IPN systems, and protect the integrity and confidentiality of the IPN software and data.

IPN INTERNET ENGINEERING INTEGRATION WITH THE IPN INTEGRATED ARCHITECTURE:  Defines the process to ensure that all components of the IPN Internet Engineering Integrated Architecture are in compliance with all IPN Integrated Architecture processes, policies, and standards.

  • Categories

  • Tweets by @IPNSIG