Policy Specification for Programmable Networks View Full Text


Ontology type: schema:Chapter     


Chapter Info

DATE

1999

AUTHORS

Morris Sloman , Emil Lupu

ABSTRACT

There is a need to be able to program network components to adapt to application requirements for quality of service, specialised application dependent routing, to increase efficiency, to support mobility and sophisticated management functionality. There are a number of different approaches to providing programmability all of which are extremely powerful and can potentially damage the network, so there is a need for clear specification of authorisation policies i.e., who is permitted to access programmable network resources or services. Obligation policies are event triggered rules which can perform actions on network components and so provide a high-level means of ‘programming’ these components. Both authorisation and obligation policies are interpreted so can be enabled, disabled or modified dynamically without shutting down components. This paper describes a notation and framework for specifying policies related to programmable networks and grouping them into roles. We show how abstract, high-level policies can be refined into a set of implementable ones and discuss the types of conflicts which can occur between policies. More... »

PAGES

73-84

Book

TITLE

Active Networks

ISBN

978-3-540-66238-9
978-3-540-48507-0

Identifiers

URI

http://scigraph.springernature.com/pub.10.1007/978-3-540-48507-0_7

DOI

http://dx.doi.org/10.1007/978-3-540-48507-0_7

DIMENSIONS

https://app.dimensions.ai/details/publication/pub.1017930188


Indexing Status Check whether this publication has been indexed by Scopus and Web Of Science using the SN Indexing Status Tool
Incoming Citations Browse incoming citations for this publication using opencitations.net

JSON-LD is the canonical representation for SciGraph data.

TIP: You can open this SciGraph record using an external JSON-LD service: JSON-LD Playground Google SDTT

[
  {
    "@context": "https://springernature.github.io/scigraph/jsonld/sgcontext.json", 
    "about": [
      {
        "id": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/08", 
        "inDefinedTermSet": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/", 
        "name": "Information and Computing Sciences", 
        "type": "DefinedTerm"
      }, 
      {
        "id": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/0806", 
        "inDefinedTermSet": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/", 
        "name": "Information Systems", 
        "type": "DefinedTerm"
      }
    ], 
    "author": [
      {
        "affiliation": {
          "alternateName": "Department of Computing, Imperial College London, SW7 2BZ, UK", 
          "id": "http://www.grid.ac/institutes/grid.7445.2", 
          "name": [
            "Department of Computing, Imperial College London, SW7 2BZ, UK"
          ], 
          "type": "Organization"
        }, 
        "familyName": "Sloman", 
        "givenName": "Morris", 
        "id": "sg:person.014167643026.41", 
        "sameAs": [
          "https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.014167643026.41"
        ], 
        "type": "Person"
      }, 
      {
        "affiliation": {
          "alternateName": "Department of Computing, Imperial College London, SW7 2BZ, UK", 
          "id": "http://www.grid.ac/institutes/grid.7445.2", 
          "name": [
            "Department of Computing, Imperial College London, SW7 2BZ, UK"
          ], 
          "type": "Organization"
        }, 
        "familyName": "Lupu", 
        "givenName": "Emil", 
        "id": "sg:person.013404167044.28", 
        "sameAs": [
          "https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.013404167044.28"
        ], 
        "type": "Person"
      }
    ], 
    "datePublished": "1999", 
    "datePublishedReg": "1999-01-01", 
    "description": "There is a need to be able to program network components to adapt to application requirements for quality of service, specialised application dependent routing, to increase efficiency, to support mobility and sophisticated management functionality. There are a number of different approaches to providing programmability all of which are extremely powerful and can potentially damage the network, so there is a need for clear specification of authorisation policies i.e., who is permitted to access programmable network resources or services. Obligation policies are event triggered rules which can perform actions on network components and so provide a high-level means of \u2018programming\u2019 these components. Both authorisation and obligation policies are interpreted so can be enabled, disabled or modified dynamically without shutting down components. This paper describes a notation and framework for specifying policies related to programmable networks and grouping them into roles. We show how abstract, high-level policies can be refined into a set of implementable ones and discuss the types of conflicts which can occur between policies.", 
    "editor": [
      {
        "familyName": "Covaci", 
        "givenName": "Stefan", 
        "type": "Person"
      }
    ], 
    "genre": "chapter", 
    "id": "sg:pub.10.1007/978-3-540-48507-0_7", 
    "isAccessibleForFree": false, 
    "isPartOf": {
      "isbn": [
        "978-3-540-66238-9", 
        "978-3-540-48507-0"
      ], 
      "name": "Active Networks", 
      "type": "Book"
    }, 
    "keywords": [
      "programmable networks", 
      "obligation policies", 
      "network components", 
      "high-level means", 
      "high-level policies", 
      "quality of service", 
      "management functionality", 
      "policy specification", 
      "network resources", 
      "authorisation policies", 
      "application requirements", 
      "network", 
      "clear specification", 
      "specification", 
      "services", 
      "different approaches", 
      "programmability", 
      "routing", 
      "programming", 
      "notation", 
      "implementable ones", 
      "functionality", 
      "framework", 
      "requirements", 
      "set", 
      "resources", 
      "rules", 
      "need", 
      "types of conflict", 
      "components", 
      "efficiency", 
      "quality", 
      "policy", 
      "authorisation", 
      "mobility", 
      "one", 
      "number", 
      "means", 
      "types", 
      "conflict", 
      "action", 
      "role", 
      "paper", 
      "approach"
    ], 
    "name": "Policy Specification for Programmable Networks", 
    "pagination": "73-84", 
    "productId": [
      {
        "name": "dimensions_id", 
        "type": "PropertyValue", 
        "value": [
          "pub.1017930188"
        ]
      }, 
      {
        "name": "doi", 
        "type": "PropertyValue", 
        "value": [
          "10.1007/978-3-540-48507-0_7"
        ]
      }
    ], 
    "publisher": {
      "name": "Springer Nature", 
      "type": "Organisation"
    }, 
    "sameAs": [
      "https://doi.org/10.1007/978-3-540-48507-0_7", 
      "https://app.dimensions.ai/details/publication/pub.1017930188"
    ], 
    "sdDataset": "chapters", 
    "sdDatePublished": "2022-10-01T06:57", 
    "sdLicense": "https://scigraph.springernature.com/explorer/license/", 
    "sdPublisher": {
      "name": "Springer Nature - SN SciGraph project", 
      "type": "Organization"
    }, 
    "sdSource": "s3://com-springernature-scigraph/baseset/20221001/entities/gbq_results/chapter/chapter_344.jsonl", 
    "type": "Chapter", 
    "url": "https://doi.org/10.1007/978-3-540-48507-0_7"
  }
]
 

Download the RDF metadata as:  json-ld nt turtle xml License info

HOW TO GET THIS DATA PROGRAMMATICALLY:

JSON-LD is a popular format for linked data which is fully compatible with JSON.

curl -H 'Accept: application/ld+json' 'https://scigraph.springernature.com/pub.10.1007/978-3-540-48507-0_7'

N-Triples is a line-based linked data format ideal for batch operations.

curl -H 'Accept: application/n-triples' 'https://scigraph.springernature.com/pub.10.1007/978-3-540-48507-0_7'

Turtle is a human-readable linked data format.

curl -H 'Accept: text/turtle' 'https://scigraph.springernature.com/pub.10.1007/978-3-540-48507-0_7'

RDF/XML is a standard XML format for linked data.

curl -H 'Accept: application/rdf+xml' 'https://scigraph.springernature.com/pub.10.1007/978-3-540-48507-0_7'


 

This table displays all metadata directly associated to this object as RDF triples.

110 TRIPLES      22 PREDICATES      69 URIs      62 LITERALS      7 BLANK NODES

Subject Predicate Object
1 sg:pub.10.1007/978-3-540-48507-0_7 schema:about anzsrc-for:08
2 anzsrc-for:0806
3 schema:author Nade63edb5c3a476781c82d0fe676ddc6
4 schema:datePublished 1999
5 schema:datePublishedReg 1999-01-01
6 schema:description There is a need to be able to program network components to adapt to application requirements for quality of service, specialised application dependent routing, to increase efficiency, to support mobility and sophisticated management functionality. There are a number of different approaches to providing programmability all of which are extremely powerful and can potentially damage the network, so there is a need for clear specification of authorisation policies i.e., who is permitted to access programmable network resources or services. Obligation policies are event triggered rules which can perform actions on network components and so provide a high-level means of ‘programming’ these components. Both authorisation and obligation policies are interpreted so can be enabled, disabled or modified dynamically without shutting down components. This paper describes a notation and framework for specifying policies related to programmable networks and grouping them into roles. We show how abstract, high-level policies can be refined into a set of implementable ones and discuss the types of conflicts which can occur between policies.
7 schema:editor Nfd7e408e2eda4adeb3cb925b6744e8a6
8 schema:genre chapter
9 schema:isAccessibleForFree false
10 schema:isPartOf N0c90e463986942ea8f5f26840b4be854
11 schema:keywords action
12 application requirements
13 approach
14 authorisation
15 authorisation policies
16 clear specification
17 components
18 conflict
19 different approaches
20 efficiency
21 framework
22 functionality
23 high-level means
24 high-level policies
25 implementable ones
26 management functionality
27 means
28 mobility
29 need
30 network
31 network components
32 network resources
33 notation
34 number
35 obligation policies
36 one
37 paper
38 policy
39 policy specification
40 programmability
41 programmable networks
42 programming
43 quality
44 quality of service
45 requirements
46 resources
47 role
48 routing
49 rules
50 services
51 set
52 specification
53 types
54 types of conflict
55 schema:name Policy Specification for Programmable Networks
56 schema:pagination 73-84
57 schema:productId N69a0ba35a6f14e5db341ff9e6a707588
58 N6c5ddaf489b64ef1a461ec91f0558f94
59 schema:publisher Ne6e4c9c433d74744b425c7b1cf7c0413
60 schema:sameAs https://app.dimensions.ai/details/publication/pub.1017930188
61 https://doi.org/10.1007/978-3-540-48507-0_7
62 schema:sdDatePublished 2022-10-01T06:57
63 schema:sdLicense https://scigraph.springernature.com/explorer/license/
64 schema:sdPublisher Nf7af7c95e3d949e0a01e50eb3378e220
65 schema:url https://doi.org/10.1007/978-3-540-48507-0_7
66 sgo:license sg:explorer/license/
67 sgo:sdDataset chapters
68 rdf:type schema:Chapter
69 N0c90e463986942ea8f5f26840b4be854 schema:isbn 978-3-540-48507-0
70 978-3-540-66238-9
71 schema:name Active Networks
72 rdf:type schema:Book
73 N4c98dc5f5d774f3eb6363faf10b9021d schema:familyName Covaci
74 schema:givenName Stefan
75 rdf:type schema:Person
76 N69a0ba35a6f14e5db341ff9e6a707588 schema:name dimensions_id
77 schema:value pub.1017930188
78 rdf:type schema:PropertyValue
79 N6c5ddaf489b64ef1a461ec91f0558f94 schema:name doi
80 schema:value 10.1007/978-3-540-48507-0_7
81 rdf:type schema:PropertyValue
82 Nade63edb5c3a476781c82d0fe676ddc6 rdf:first sg:person.014167643026.41
83 rdf:rest Nddcd0dcb92954d018fed039b074ab6ab
84 Nddcd0dcb92954d018fed039b074ab6ab rdf:first sg:person.013404167044.28
85 rdf:rest rdf:nil
86 Ne6e4c9c433d74744b425c7b1cf7c0413 schema:name Springer Nature
87 rdf:type schema:Organisation
88 Nf7af7c95e3d949e0a01e50eb3378e220 schema:name Springer Nature - SN SciGraph project
89 rdf:type schema:Organization
90 Nfd7e408e2eda4adeb3cb925b6744e8a6 rdf:first N4c98dc5f5d774f3eb6363faf10b9021d
91 rdf:rest rdf:nil
92 anzsrc-for:08 schema:inDefinedTermSet anzsrc-for:
93 schema:name Information and Computing Sciences
94 rdf:type schema:DefinedTerm
95 anzsrc-for:0806 schema:inDefinedTermSet anzsrc-for:
96 schema:name Information Systems
97 rdf:type schema:DefinedTerm
98 sg:person.013404167044.28 schema:affiliation grid-institutes:grid.7445.2
99 schema:familyName Lupu
100 schema:givenName Emil
101 schema:sameAs https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.013404167044.28
102 rdf:type schema:Person
103 sg:person.014167643026.41 schema:affiliation grid-institutes:grid.7445.2
104 schema:familyName Sloman
105 schema:givenName Morris
106 schema:sameAs https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.014167643026.41
107 rdf:type schema:Person
108 grid-institutes:grid.7445.2 schema:alternateName Department of Computing, Imperial College London, SW7 2BZ, UK
109 schema:name Department of Computing, Imperial College London, SW7 2BZ, UK
110 rdf:type schema:Organization
 




Preview window. Press ESC to close (or click here)


...