text:
[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits] [IPR]
Versions: 00 01 02 03 04 05 06 07 08 draft-ietf-6man-segment-routing-header
Network Working Group                                    S. Previdi, Ed.
Internet-Draft                                               C. Filsfils
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: May 16, 2015                                           B. Field
I. Leung
IPv6 Segment Routing Header (SRH)
draft-previdi-6man-segment-routing-header-04
Segment Routing (SR) allows a node to steer a packet through a
controlled set of instructions, called segments, by prepending a SR
header to the packet.  A segment can represent any instruction,
topological or service-based.  SR allows to enforce a flow through
any path (topological, or application/service based) while
maintaining per-flow state only at the ingress node to the SR domain.
Segment Routing can be applied to the IPv6 data plane with the
addition of a new type of Routing Extension Header.  This draft
describes the Segment Routing Extension Header Type and how it is
used by SR capable nodes.
Requirements Language
document are to be interpreted as described in RFC 2119 [RFC2119].
Previdi, et al.           Expires May 16, 2015                  [Page 1]
Internet-Draft      IPv6 Segment Routing Header (SRH)      November 2014
This Internet-Draft will expire on May 16, 2015.
1.  Structure of this document  . . . . . . . . . . . . . . . . .   3
2.  Segment Routing Documents . . . . . . . . . . . . . . . . . .   3
3.1.  Data Planes supporting Segment Routing  . . . . . . . . .   4
3.2.  Illustration  . . . . . . . . . . . . . . . . . . . . . .   4
4.  Abstract Routing Model  . . . . . . . . . . . . . . . . . . .   7
4.1.  Segment Routing Global Block (SRGB) . . . . . . . . . . .   8
4.2.  Traffic Engineering with SR . . . . . . . . . . . . . . .   9
4.3.  Segment Routing Database  . . . . . . . . . . . . . . . .  10
5.  IPv6 Instantiation of Segment Routing . . . . . . . . . . . .  10
5.1.  Segment Identifiers (SIDs) and SRGB . . . . . . . . . . .  10
5.1.1.  Node-SID  . . . . . . . . . . . . . . . . . . . . . .  11
5.1.2.  Adjacency-SID . . . . . . . . . . . . . . . . . . . .  11
5.2.  Segment Routing Extension Header (SRH)  . . . . . . . . .  11
5.2.1.  SRH and RFC2460 behavior  . . . . . . . . . . . . . .  15
5.2.2.  SRH Optimization  . . . . . . . . . . . . . . . . . .  15
6.  SRH Procedures  . . . . . . . . . . . . . . . . . . . . . . .  16
6.1.  Segment Routing Operations  . . . . . . . . . . . . . . .  16
6.2.  Segment Routing Node Functions  . . . . . . . . . . . . .  16
6.2.1.  Ingress SR Node . . . . . . . . . . . . . . . . . . .  17
6.2.2.  Transit Non-SR Capable Node . . . . . . . . . . . . .  18
6.2.3.  SR Intra Segment Transit Node . . . . . . . . . . . .  18
6.2.4.  SR Segment Endpoint Node  . . . . . . . . . . . . . .  19
6.3.  FRR Flag Settings . . . . . . . . . . . . . . . . . . . .  19
7.  SR and Tunneling  . . . . . . . . . . . . . . . . . . . . . .  19
8.  Example Use Case  . . . . . . . . . . . . . . . . . . . . . .  20
10. Manageability Considerations  . . . . . . . . . . . . . . . .  22
11. Security Considerations . . . . . . . . . . . . . . . . . . .  22
12. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  22
13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  22
14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
14.1.  Normative References . . . . . . . . . . . . . . . . . .  22
14.2.  Informative References . . . . . . . . . . . . . . . . .  22
1.  Structure of this document
Section 3 gives an introduction on SR for IPv6 networks.
Section 4 describes the Segment Routing abstract model.
Section 5 defines the Segment Routing Header (SRH) allowing
instantiation of SR over IPv6 dataplane.
Section 6 details the procedures of the Segment Routing Header.
2.  Segment Routing Documents
Segment Routing terminology is defined in
[I-D.filsfils-spring-segment-routing].
Segment Routing use cases are described in
[I-D.filsfils-spring-segment-routing-use-cases].
Segment Routing IPv6 use cases are described in
[I-D.ietf-spring-ipv6-use-cases].
Segment Routing protocol extensions are defined in
[I-D.ietf-isis-segment-routing-extensions], and
[I-D.psenak-ospf-segment-routing-ospfv3-extension].
The security mechanisms of the Segment Routing Header (SRH) are
described in [I-D.vyncke-6man-segment-routing-security].
Segment Routing (SR), defined in
[I-D.filsfils-spring-segment-routing], allows a node to steer a
packet through a controlled set of instructions, called segments, by
prepending a SR header to the packet.  A segment can represent any
instruction, topological or service-based.  SR allows to enforce a
flow through any path (topological or service/application based)
while maintaining per-flow state only at the ingress node to the SR
domain.  Segments can be derived from different components: IGP, BGP,
Services, Contexts, Locators, etc.  The list of segment forming the
path is called the Segment List and is encoded in the packet header.
SR allows the use of strict and loose source based routing paradigms
without requiring any additional signaling protocols in the
infrastructure hence delivering an excellent scalability property.
The source based routing model described in
[I-D.filsfils-spring-segment-routing] is inherited from the ones
proposed by [RFC1940] and [RFC2460].  The source based routing model
offers the support for explicit routing capability.
3.1.  Data Planes supporting Segment Routing
Segment Routing (SR), can be instantiated over MPLS
([I-D.filsfils-spring-segment-routing-mpls]) and IPv6.  This document
defines its instantiation over the IPv6 data-plane based on the use-
cases defined in [I-D.ietf-spring-ipv6-use-cases].
Segment Routing for IPv6 (SR-IPv6) is required in networks where MPLS
data-plane is not used or, when combined with SR-MPLS, in networks
where MPLS is used in the core and IPv6 is used at the edge (home
networks, datacenters).
This document defines a new type of Routing Header (originally
defined in [RFC2460]) called the Segment Routing Header (SRH) in
order to convey the Segment List in the packet header as defined in
[I-D.filsfils-spring-segment-routing].  Mechanisms through which
segment are known and advertised are outside the scope of this
3.2.  Illustration
In the context of Figure 1 where all the links have the same IGP
cost, let us assume that a packet P enters the SR domain at an
ingress edge router I and that the operator requests the following
requirements for packet P:
The local service S offered by node B must be applied to packet P.
The links AB and CE cannot be used to transport the packet P.
Any node N along the journey of the packet should be able to
determine where the packet P entered the SR domain and where it
will exit.  The intermediate node should be able to determine the
paths from the ingress edge router to itself, and from itself to
the egress edge router.
Per-flow State for packet P should only be created at the ingress
edge router.
The operator can forbid, for security reasons, anyone outside the
operator domain to exploit its intra-domain SR capabilities.
I---A---B---C---E
\  |  / \ /
\ | /   F
\|/
Figure 1: An illustration of SR properties
All these properties may be realized by instructing the ingress SR
edge router I to push the following abstract SR header on the packet
+---------------------------------------------------------------+
|                                   |                           |
|      Abstract SR Header           |                           |
| {SD, SB, SS, SF, SE}, Ptr, SI, SE |        Transported        |
|  ^                     |          |           Packet          |
|  |                     |          |             P             |
|  +---------------------+          |                           |
Figure 2: Packet P at node I
The abstract SR header contains a source route encoded as a list of
segments {SD, SB, SS, SF, SE}, a pointer (Ptr) and the identification
of the ingress and egress SR edge routers (segments SI and SE).
A segment identifies a topological instruction or a service
instruction.  A segment can either be global or local.  The
instruction associated with a global segment is recognized and
executed by any SR-capable node in the domain.  The instruction
associated with a local segment is only supported by the specific
node that originates it.
Let us assume some IGP (i.e.: ISIS and OSPF) extensions to define a
"Node Segment" as a global instruction within the IGP domain to
forward a packet along the shortest path to the specified node.  Let
us further assume that within the SR domain illustrated in Figure 1,
segments SI, SD, SB, SE and SF respectively identify IGP node
segments to I, D, B, E and F.
Let us assume that node B identifies its local service S with local
segment SS.
With all of this in mind, let us describe the journey of the packet
The packet P reaches the ingress SR edge router.  I pushes the SR
header illustrated in Figure 2 and sets the pointer to the first
segment of the list (SD).
SD is an instruction recognized by all the nodes in the SR domain
which causes the packet to be forwarded along the shortest path to D.
Once at D, the pointer is incremented and the next segment is
executed (SB).
SB is an instruction recognized by all the nodes in the SR domain
which causes the packet to be forwarded along the shortest path to B.
Once at B, the pointer is incremented and the next segment is
executed (SS).
SS is an instruction only recognized by node B which causes the
packet to receive service S.
Once the service applied, the next segment is executed (SF) which
causes the packet to be forwarded along the shortest path to F.
Once at F, the pointer is incremented and the next segment is
executed (SE).
SE is an instruction recognized by all the nodes in the SR domain
which causes the packet to be forwarded along the shortest path to E.
E then removes the SR header and the packet continues its journey
outside the SR domain.
All of the requirements are met.
First, the packet P has not used links AB and CE: the shortest-path
from I to D is I-A-D, the shortest-path from D to B is D-B, the
shortest-path from B to F is B-C-F and the shortest-path from F to E
is F-E, hence the packet path through the SR domain is I-A-D-B-C-F-E
and the links AB and CE have been avoided.
Second, the service S supported by B has been applied on packet P.
Third, any node along the packet path is able to identify the service
and topological journey of the packet within the SR domain.  For
example, node C receives the packet illustrated in Figure 3 and hence
is able to infer where the packet entered the SR domain (SI), how it
got up to itself {SD, SB, SS, SE}, where it will exit the SR domain
(SE) and how it will do so {SF, SE}.
|           SR Header               |                           |
|               ^        |          |           Packet          |
|               |        |          |             P             |
|               +--------+          |                           |
Figure 3: Packet P at node C
Fourth, only node I maintains per-flow state for packet P.  The
entire program of topological and service instructions to be executed
by the SR domain on packet P is encoded by the ingress edge router I
in the SR header in the form of a list of segments where each segment
identifies a specific instruction.  No further per-flow state is
required along the packet path.  The per-flow state is in the SR
header and travels with the packet.  Intermediate nodes only hold
states related to the IGP global node segments and the local IGP
adjacency segments.  These segments are not per-flow specific and
hence scale very well.  Typically, an intermediate node would
maintain in the order of 100's to 1000's global node segments and in
the order of 10's to 100 of local adjacency segments.  Typically the
SR IGP forwarding table is expected to be much less than 10000
entries.
Fifth, the SR header is inserted at the entrance to the domain and
removed at the exit of the operator domain.  For security reasons,
the operator can forbid anyone outside its domain to use its intra-
domain SR capability.
4.  Abstract Routing Model
At the entrance of the SR domain, the ingress SR edge router pushes
the SR header on top of the packet.  At the exit of the SR domain,
the egress SR edge router removes the SR header.
The abstract SR header contains an ordered list of segments, a
pointer identifying the next segment to process and the
identifications of the ingress and egress SR edge routers on the path
of this packet.  The pointer identifies the segment that MUST be used
by the receiving router to process the packet.  This segment is
called the active segment.
A property of SR is that the entire source route of the packet,
including the identity of the ingress and egress edge routers is
always available with the packet.  This allows for interesting
accounting and service applications.
We define three SR-header operations:
"PUSH": an SR header is pushed on an IP packet, or additional
segments are added at the head of the segment list.  The pointer
is moved to the first entry of the added segments.
"NEXT": the active segment is completed, the pointer is moved to
the next segment in the list.
"CONTINUE": the active segment is not completed, the pointer is
left unchanged.
In the future, other SR-header management operations may be defined.
As the packet travels through the SR domain, the pointer is
incremented through the ordered list of segments and the source route
encoded by the SR ingress edge node is executed.
A node processes an incoming packet according to the instruction
associated with the active segment.
Any instruction might be associated with a segment: for example, an
intra-domain topological strict or loose forwarding instruction, a
service instruction, etc.
At minimum, a segment instruction must define two elements: the
identity of the next-hop to forward the packet to (this could be the
same node or a context within the node) and which SR-header
management operation to execute.
Each segment is known in the network through a Segment Identifier
(SID).  The terms "segment" and "SID" are interchangeable.
4.1.  Segment Routing Global Block (SRGB)
In the SR abstract model, a segment is identified by a Segment
Routing Identifier (SID).  The SR abstract model doesn't mandate a
specific format for the SID (IPv6 address or other formats).
In Segment Routing IPv6 the SID is an IPv6 address.  Therefore, the
SRGB is materialized by the global IPv6 address space which
represents the set of IPv6 routable addresses in the SR domain.  The
following rules apply:
o  Each node of the SR domain MUST be configured with the Segment
Routing Global Block (SRGB).
o  All global segments must be allocated from the SRGB.  Any SR
capable node MUST be able to process any global segment advertised
by any other node within the SR domain.
o  Any segment outside the SRGB has a local significance and is
called a "local segment".  An SR-capable node MUST be able to
process the local segments it originates.  An SR-capable node MUST
NOT support the instruction associated with a local segment
originated by a remote node.
4.2.  Traffic Engineering with SR
An SR Traffic Engineering policy is composed of two elements: a flow
classification and a segment-list to prepend on the packets of the
flow.
In SR, this per-flow state only exists at the ingress edge node where
the policy is defined and the SR header is pushed.
It is outside the scope of the document to define the process that
leads to the instantiation at a node N of an SR Traffic Engineering
[I-D.filsfils-spring-segment-routing-use-cases] illustrates various
N is deriving this policy automatically (e.g.  FRR).
N is provisioned explicitly by the operator.
N is provisioned by a controller or server (e.g.: SDN Controller).
N is provisioned by the operator with a high-level policy which is
mapped into a path thanks to a local CSPF-based computation (e.g.
affinity/SRLG exclusion).
N could also be provisioned by other means.
[I-D.filsfils-spring-segment-routing-use-cases] explains why the
majority of use-cases require very short segment-lists, hence
minimizing the performance impact, if any, of inserting and
transporting the segment list.
A SDN controller, which desires to instantiate at node N an SR
Traffic Engineering policy, collects the SR capability of node N such
as to ensure that the policy meets its capability.
4.3.  Segment Routing Database
The Segment routing Database (SRDB) is a set of entries where each
entry is identified by a SID.  The instruction associated with each
entry at least defines the identity of the next-hop to which the
packet should be forwarded and what operation should be performed on
the SR header (PUSH, CONTINUE, NEXT).
+---------+-----------+---------------------------------+
| Segment |  Next-Hop |  SR Header operation            |
|   Sk    |     M     | CONTINUE                        |
|   Sj    |     N     | NEXT                            |
|   Sl    | NAT Srvc  | NEXT                            |
|   Sm    |  FW srvc  | NEXT                            |
|   Sn    |     Q     | NEXT                            |
|  etc.   |   etc.    | etc.                            |
Figure 4: SR Database
Each SR-capable node maintains its local SRDB.  SRDB entries can
either derive from local policy or from protocol segment
5.  IPv6 Instantiation of Segment Routing
5.1.  Segment Identifiers (SIDs) and SRGB
Segment Routing, as described in
[I-D.filsfils-spring-segment-routing], defines Node-SID and
Adjacency-SID.  When SR is used over IPv6 data-plane the following
applies.
The SRGB is the global IPv6 address space which represents the set of
IPv6 routable addresses in the SR domain.
Node SIDs are IPv6 addresses part of the SRGB (i.e.: routable
addresses).  Adjacency-SIDs are IPv6 addresses which may not be part
of the global IPv6 address space.
Previdi, et al.           Expires May 16, 2015                 [Page 10]
5.1.1.  Node-SID
The Node-SID identifies a node.  With SR-IPv6 the Node-SID is an IPv6
prefix that the operator configured on the node and that is used as
the node identifier.  Typically, in case of a router, this is the
IPv6 address of the node loopback interface.  Therefore, SR-IPv6 does
not require any additional SID advertisement for the Node Segment.
The Node-SID is in fact the IPv6 address of the node.
5.1.2.  Adjacency-SID
In the SR architecture defined in
[I-D.filsfils-spring-segment-routing] the Adjacency-SID (or Adj-SID)
identifies a given interface and may be local or global (depending on
how it is advertised).  A node may advertise one (or more) Adj-SIDs
allocated to a given interface so to force the forwarding of the
packet (when received with that particular Adj-SID) into the
interface regardless the routing entry for the packet destination.
The semantic of the Adj-SID is:
Send out the packet to the interface this prefix is allocated to.
When SR is applied to IPv6, any SID is in a global IPv6 address and
therefore, an Adj-SID has a global significance (i.e.: the IPv6
address representing the SID is a global address).  In other words, a
node that advertises the Adj-SID in the form of a global IPv6 address
representing the link/adjacency the packet has to be forwarded to,
will apply to the Adj-SID a global significance.
Advertisement of Adj-SID may be done using multiple mechanisms among
which the ones described in ISIS and OSPF protocol extensions:
[I-D.ietf-isis-segment-routing-extensions] and
[I-D.psenak-ospf-segment-routing-ospfv3-extension].  The distinction
between local and global significance of the Adj-SID is given in the
encoding of the Adj-SID advertisement.
5.2.  Segment Routing Extension Header (SRH)
A new type of the Routing Header (originally defined in [RFC2460]) is
defined: the Segment Routing Header (SRH) which has a new Routing
Type, (suggested value 4) to be assigned by IANA.
As an example, if an explicit path is to be constructed across a core
network running ISIS or OSPF, the segment list will contain SIDs
representing the nodes across the path (loose or strict) which,
usually, are the IPv6 loopback interface address of each node.  If
the path is across service or application entities, the segment list
contains the IPv6 addresses of these services or application
The Segment Routing Header (SRH) is defined as follows:
| Next Header   |  Hdr Ext Len  | Routing Type  | Next Segment  |
| Last Segment  |             Flags             |  HMAC Key ID  |
|            Segment List[0] (128 bits ipv6 address)            |
|            Segment List[n] (128 bits ipv6 address)            |
|            Policy List[0] (optional)                          |
|                       HMAC (256 bits)                         |
|                        (optional)                             |
o  Next Header: 8-bit selector.  Identifies the type of header
immediately following the SRH.
o  Hdr Ext Len: 8-bit unsigned integer, is the length of the SRH
header in 8-octet units, not including the first 8 octets.
o  Routing Type: TBD, to be assigned by IANA (suggested value: 4).
o  Next Segment (originally defined as "Segments Left" in [RFC2460]):
index, in the Segment List, of the next active segment (according
to terminology defined in [I-D.filsfils-spring-segment-routing])
in the SRH.  Note that this differs from the semantic defined in
the Routing Header specification ([RFC2460] defines it as
"Segments Left").  Therefore, in the Segment Routing context, the
"Segments Left" field is renamed as "Next Segment".
o  Last Segment: index, in the Segment List, of the next active
segment of the last segment of the path in the SRH.
o  Flags: 16 bits of flags.  Following flags are defined:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|C|P|R|R|    Policy Flags       |
C-flag: Clean-up flag.  Set when the SRH has to be removed from
the packet when packet reaches the last segment.
P-flag: Protected flag.  Set when the packet has been rerouted
through FRR mechanism by a SR endpoint node.  See Section 6.3
R-flags.  Reserved and for future use.
Policy List flags.  Define the type of the IPv6 addresses
encoded into the Policy List (see below).  The following have
been defined:
Bits 4-6: determine the type of the first element after the
segment list.
Bits 7-9: determine the type of the second element.
Bits 10-12: determine the type of the third element.
Bits 13-15: determine the type of the fourth element.
The following values are used for the type:
0x0: Not present.  If value is set to 0x0, it means the
element represented by these bits is not present.
0x1: SR Ingress.
0x2: SR Egress.
0x3: Original Source Address.
o  HMAC Key ID and HMAC field, and their use are defined in
[I-D.vyncke-6man-segment-routing-security].
o  Segment List[n]: 128 bit IPv6 addresses representing the nth
segment of the path.
o  Policy List.  Optional addresses representing specific nodes in
the SR path such as:
SR Ingress: a 128 bit generic identifier representing the
ingress in the SR domain (i.e.: it needs not to be a valid IPv6
SR Egress: a 128 bit generic identifier representing the egress
in the SR domain (i.e.: it needs not to be a valid IPv6
Original Source Address: IPv6 address originally present in the
SA field of the packet.
The segments in the Policy List are encoded after the segment list
and they are optional.  If none are in the SRH, all bits of the
Policy List Flags MUST be set to 0x0.
5.2.1.  SRH and RFC2460 behavior
The SRH being a new type of the Routing Header, it also has the same
SHOULD only appear once in the packet.
Only the router whose address is in the DA field of the packet
header MUST inspect the SRH.
Therefore, Segment Routing in IPv6 networks implies that the segment
identifier (i.e.: the IPv6 address of the segment) is moved into the
DA of the packet.
The DA of the packet changes at each segment termination/completion
and therefore the original DA of the packet MUST be encoded as the
last segment of the path.
As illustrated in Section 3.2, nodes that are within the path of a
segment will forward packets based on the DA of the packet without
inspecting the SRH.  This ensures full interoperability between SR-
capable and non-SR-capable nodes.
5.2.2.  SRH Optimization
In order to optimize the way the SRH and, more precisely, the Segment
List is processed by SR nodes, it is desirable that most of the
necessary information of the SL is placed at the top of the list so
to avoid reading the whole content of the SRH prior to make
With this in mind, when the SRH is created and the segment list is
inserted, the order of the segments in the segment list is as
o  The Next Segment field points to the next segment to be examined
(offset within the SRH).
o  The first segment being encoded in the DA by the ingress node, it
doesn't need to sit in the first position of the list.
o  Hence, the first element of the segment list is the second segment
of the path so that, when the packet reaches the end of the first
segment, the node inspecting the SRH will find the second segment
at the beginning of the segment list.
o  The other segments of the path are encoded sequentially after the
second segment.
o  The last segment of the path is the original DA address.
o  The last segment in the Segment List is used to encode the first
segment.  This segment will never be inspected anyway (at least
not for forwarding purposes).
6.  SRH Procedures
In this section we describe the different procedures on the SRH.
6.1.  Segment Routing Operations
When Segment Routing is instantiated over the IPv6 data plane the
following applies:
o  The segment list is encoded in the SRH.
o  The active segment is in the destination address of the packet.
o  The Segment Routing CONTINUE operation (as described in
[I-D.filsfils-spring-segment-routing]) is implemented as a
regular/plain IPv6 operation consisting of DA based forwarding.
o  The NEXT operation is implemented through the update of the DA
with the value represented by the Next Segment field in the SRH.
o  The PUSH operation is implemented through the insertion of the SRH
or the insertion of additional segments in the SRH segment list.
6.2.  Segment Routing Node Functions
SR packets are forwarded to segments endpoints (i.e.: nodes whose
address is in the DA field of the packet).  The segment endpoint,
when receiving a SR packet destined to itself, does:
o  Inspect the SRH.
o  Determine the next segment.
o  Update the SRH (or, if requested, remove the SRH from the packet).
o  Update the DA.
o  Send the packet to the next segment.
The procedures applied to the SRH are related to the node function.
Following nodes functions are defined:
Ingress SR Node.
Transit Non-SR Node.
Transit SR Intra Segment Node.
SR Endpoint Node.
6.2.1.  Ingress SR Node
Ingress Node can be a router at the edge of the SR domain or a SR-
capable host.  The ingress SR node may obtain the segment list by
Local path computation.
Local configuration.
Interaction with an SDN controller delivering the path as a
complete SRH.
Any other mechanism (mechanisms through which the path is acquired
are outside the scope of this document).
When creating the SRH (either at ingress node or in the SDN
controller) the following is done:
Next Header and Hdr Ext Len fields are set according to [RFC2460].
Routing Type field is set as TBD (SRH).
The DA of the packet is set with the address of the FIRST segment
of the path.
Next Segment field contains the offset of the SECOND segment of
the path which is encoded in the FIRST position of the segment
list.  The segment list is encoded as follows:
The first element of the list contains the second segment (as
stated above).
All subsequent segments are encoded following the second
The original DA of the packet is encoded as the last segment of
the path (which is NOT the last segment of the segment list).
The last segment of the segment list is the FIRST segment of
the path.
Last Segment field contains the offset of the last segment of the
path (i.e.: the original DA of the packet).
The packet is sent out to the first segment.
6.2.1.1.  Security at Ingress
The procedures related to the Segment Routing security are detailed
in [I-D.vyncke-6man-segment-routing-security].
In the case where the SR domain boundaries are not under control of
the network operator (e.g.: when the SR domain edge is in a home
network), it is important to authenticate and validate the content of
any SRH being received by the network operator.  In such case, the
security procedure described in
[I-D.vyncke-6man-segment-routing-security] is to be used.
The ingress node (e.g.: the host in the home network) requests the
SRH from a control system (e.g.: an SDN controller) which delivers
the SRH with its HMAC signature on it.
Then, the home network host can send out SR packets (with an SRH on
it) that will be validated at the ingress of the network operator
The ingress node of the network operator infrastructure, is
configured in order to validate the incoming SRH HMACs in order to
allow only packets having correct SRH according to their SA/DA
addresses.
6.2.2.  Transit Non-SR Capable Node
SR is interoperable with plain IPv6 forwarding.  Any non SR-capable
node will forward SR packets solely based on the DA.  There's no SRH
inspection.  This ensures full interoperability between SR and non-SR
nodes.
6.2.3.  SR Intra Segment Transit Node
Only the node whose address is in DA inspects and processes the SRH
(according to [RFC2460]).  An intra segment transit node is not in
the DA and its forwarding is based on DA and its SR-IPv6 FIB.
6.2.4.  SR Segment Endpoint Node
The SR segment endpoint node is the node whose address is in the DA.
The segment endpoint node inspects the SRH and does:
1.   IF DA = myself (segment endpoint)
2.      IF Next Segment <> Last Segment THEN
update DA with Next Segment
increment Next Segment
3.      ELSE IF Last Segment <> DA THEN
IF Clean-up bit is set THEN remove the SRH
4.      ELSE give the packet to next PID (application)
End of processing.
5.   Forward the packet out
6.3.  FRR Flag Settings
A node supporting SR and doing Fast Reroute (as described in
[I-D.filsfils-spring-segment-routing-use-cases], when rerouting
packets through FRR mechanisms, SHOULD inspect the rerouted packet
header and look for the SRH.  If the SRH is present, the rerouting
node SHOULD set the Protected bit on all rerouted packets.
7.  SR and Tunneling
Encapsulation can be realized in two different ways with SR-IPv6:
Outer encapsulation.
SRH with SA/DA original addresses.
Outer encapsulation tunneling is the traditional method where an
additional IPv6 header is prepended to the packet.  The original IPv6
header being encapsulated, everything is preserved and the packet is
switched/routed according to the outer header (that could contain a
SRH).
SRH allows encoding both original SA and DA and therefore, hence an
operator may decide to change the SA/DA at ingress and restore them
at egress.  This can be achieved without outer encapsulation, by
changing SA/DA and encoding the original values in the Segment List
(the last segment of the path being the original DA) and in the
Policy List (original SA).
8.  Example Use Case
A more detailed description of use cases are available in
[I-D.ietf-spring-ipv6-use-cases].  In this section, a simple SR-IPv6
example is illustrated.
In the topology described in Figure 6 it is assumed an end-to-end SR
deployment.  Therefore SR is supported by all nodes from A to J.
Home Network |          Backbone         |    Datacenter
|                           |
|   +---+   +---+   +---+   |   +---+   |
+---|---| C |---| D |---| E |---|---| I |---|
|   |   +---+   +---+   +---+   |   +---+   |
|   |     |       |       |     |     |     |  +---+
+---+   +---+ |     |       |       |     |     |     |--| X |
| A |---| B | |   +---+   +---+   +---+   |   +---+   |  +---+
+---+   +---+ |   | F |---| G |---| H |---|---| J |---|
|        +-----------+
|    SDN    |
| Orch/Ctlr |
+-----------+
Figure 6: Sample SR topology
The following workflow applies to packets sent by host A and destined
to server X.
. Host A sends a request for a path to server X to the SDN
controller or orchestration system.
. The SDN controller/orchestrator builds a SRH with:
. Segment List: C, F, J, X
. HMAC
that satisfies the requirements expressed in the request
by host A and based on policies applicable to host A.
. Host A receives the SRH and insert it into the packet.
The packet has now:
. SA: A
. DA: C
. SRH with
. SL: F,J,X,C
. PL: C (ingress), J (egress)
Note that X is the last segment and C is the
first segment (encoded at the end of the SL).
. When packet arrives in C (first segment), C does:
. Validate the HMAC of the SRH.
. Update the DA with the next segment (found in SRH):
DA is set to F.
. Forward the packet to F.
. Packet arrives in F which inspects the SRH and find the
next segment:
. DA is set to J.
. Packet travels across G and H nodes which do plain
IPv6 forwarding based on DA. No inspection of SRH needs
to be done in these nodes. However, any SR capable node
is allowed to set the Protected bit in case of FRR
protection.
. Packet arrives in J where two options are available
depending on the settings of the cleanup bit set in the
SRH:
. If the cleanup bit is set, then node J will strip out
the SRH from the packet, set the DA as X and send
the packet out.
. If the clean-up bit is not set, the DA is set to X
and the packet is sent out with the SRH.
The packet arrives in the server that may or may not support SR.  The
return traffic, from server to host, may be sent using the same
procedures.
10.  Manageability Considerations
11.  Security Considerations
Security mechanisms applied to Segment Routing over IPv6 networks are
detailed in [I-D.vyncke-6man-segment-routing-security].
12.  Contributors
The authors would like to thank Dave Barach, John Leddy, John
Brzozowski, Pierre Francois, Nagendra Kumar, Mark Townsley, Christian
Martin, Roberta Maglione, Eric Vyncke, James Connolly and David
Lebrun for their contribution to this document.
13.  Acknowledgements
14.  References
14.1.  Normative References
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
14.2.  Informative References
[I-D.filsfils-spring-segment-routing]
Filsfils, C., Previdi, S., Bashandy, A., Decraene, B.,
Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R.,
Ytti, S., Henderickx, W., Tantsura, J., and E. Crabbe,
"Segment Routing Architecture", draft-filsfils-spring-
segment-routing-04 (work in progress), July 2014.
[I-D.filsfils-spring-segment-routing-mpls]
"Segment Routing with MPLS data plane", draft-filsfils-
spring-segment-routing-mpls-03 (work in progress), August
[I-D.filsfils-spring-segment-routing-use-cases]
Filsfils, C., Francois, P., Previdi, S., Decraene, B.,
Ytti, S., Henderickx, W., Tantsura, J., Kini, S., and E.
Crabbe, "Segment Routing Use Cases", draft-filsfils-
spring-segment-routing-use-cases-01 (work in progress),
October 2014.
[I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Filsfils, C., Bashandy, A., Gredler, H.,
Litkowski, S., Decraene, B., and J. Tantsura, "IS-IS
Extensions for Segment Routing", draft-ietf-isis-segment-
routing-extensions-03 (work in progress), October 2014.
[I-D.ietf-spring-ipv6-use-cases]
Brzozowski, J., Leddy, J., Leung, I., Previdi, S.,
Townsley, W., Martin, C., Filsfils, C., and R. Maglione,
"IPv6 SPRING Use Cases", draft-ietf-spring-ipv6-use-
cases-02 (work in progress), October 2014.
[I-D.psenak-ospf-segment-routing-ospfv3-extension]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3
Extensions for Segment Routing", draft-psenak-ospf-
segment-routing-ospfv3-extension-02 (work in progress),
[I-D.vyncke-6man-segment-routing-security]
Vyncke, E. and S. Previdi, "IPv6 Segment Routing Header
(SRH) Security Considerations", July 2014.
[RFC1940]  Estrin, D., Li, T., Rekhter, Y., Varadhan, K., and D.
Zappala, "Source Demand Routing: Packet Format and
Forwarding Specification (Version 1)", RFC 1940, May 1996.
Stefano Previdi (editor)
Via Del Serafico, 200
Rome  00142
Email: sprevidi@cisco.com
Clarence Filsfils
Email: cfilsfil@cisco.com
Brian Field
4100 East Dry Creek Road
Centennial, CO  80122
Email: Brian_Field@cable.comcast.com
Ida Leung
Brampton, ON  L6T 0C1
Email: Ida.Leung@rci.rogers.com


Disclaimer: Intentional Use of Bad Metaphor, Read at Your Own Risk.
Naturally, Scarlet Whisper has to crack a few safes/vaults/heads to get the jewels.
As her mild-mannered alter ego, I'm more into cerebral lock picking. Lately, I've been struggling to unlock the secrets of characterization and emotional tension.
I have to deliver more than that. My characters can't just move from one scene like CGI ninjas on a green screen. My tale needs depth and heart. The reader needs to get inside the mind of the protagonist.
Whoa…sometimes, I don't feel up to the task of this whole writing gig.
It's a good thing I have writing mentors. The League of Extraordinary Writers, the superfriends who meet every Wednesday for DFWWW and IHOP post mortem are my saving grace.
Their advice and critique is priceless. The tips and tricks are like a locksmith's tools. I can use them to crack the writing code. I can listen and learn and read examples of good stuff. Once the door is open, it's like I'm rolling around in a pile of greenbacks and sparkly stones.
All week, I've been marking up passages of favorite books and posts. I'm analyzing good passages and taking notes.
I'd love to know what writing obstacles you struggle with. What has helped YOU?
Hungry for More? Try my banana pudding, a dish modeled after one of Elvis Presley's favorite desserts.
In a large bowl, blend pudding mix with milk (use a wire whisk). Add sour cream and half the cool whip. Mix well. Set aside. In a large bowl or dish, layer in the following order: cookies, bananas and pudding mixture. Top with remaining cool whip.
I don't know which sounds more decadent, your metaphors or your yummy banana pudding! I couldn't do without my local writers group either – priceless.
Marsha: That's awesome. Seriously, my workshop is usually the highlight of my week. People talk about writing being such a solitary thing. Yes, the actual behind in the chair, hands on the keyboard gig is an individual process, but camaraderie with fellow writers is such a wonderful thing.
I've learned so much by being online the past year or so. AQ is invaluable. Then there are the blogs of writers, agents and editors. When I'm stuck or need inspiration that's where I head.
I finally broke through & got my ending down today – after multiple bleh attempts. Listening to online advice about letting the characters guide, taking time.. all helped.
Congrats, Jemi! Is this the steampunk project, or is this a new one?
Wow. I mean, I knew the Scarlett Whisperer was into the occasional lock/safe/head breaking–and the occasional late book beating, but wow. The insight into picking the lock of your character's brains is awesome. I didn't realize that's what we'd been working on doing…you put it in such awesome perspective. I'm tickled I'm in your writing group and thankful to have your perspective! Viva la IHOP!
You're very lucky to have the IHOP Crew. Beta readers are so important. My face to face writing buddy just got married and moved.
Cat: I'm so sorry! You'll have to be an honorary member of the IHOP crew, in abstentia!


text:
AJAD Volume 3 Issue No. 1&2 December 2006
Rural Credit Markets in Myanmar: A Study of Formal and Non-Formal Lenders
Tomoko Kaino
This paper conducts an empirical investigation of the rural credit market in Myanmar to help guide policy formulation on the microfinance operations in the country. Specifically, it looks into the determinants of credit demand and of rationing loans at the household level, and identifies the...
Sustainability and Governance of Microfinance Institutions: Recent Experiences and Some Lessons for Southeast Asia
Ganesh Thapa
Microfinance has become an important tool for poverty reduction in many parts of the world, including Asia and the Pacific region. Microfinance institutions (MFIs) target the poor through innovative approaches which include group lending, progressive lending, regular repayment schedules, and...
MNEs and the Global Integration of Thailand's Processed Food Exports: A Firm-Level Study
Archanun U. Kohpaiboon
This paper presents the findings of a firm-level case study examining the role of multinational enterprises (MNEs) in processed food exports from Thailand. The discussion covers both FDI (foreign direct investment) and non-FDI channels of MNE involvement in the export of four major items, namely...
The Ecological and Economic Aspects of the Multifunctional Role of Agroecosystems
Percy E. Sajise and Asa Jose U. Sajise
Current perceptions about agriculture-based systems are rooted in an assessment of their negative and positive externalities, as well as their tremendous influence in the cultural and religious values of communities. Among the emerging concerns is how to integrate this view of the multi-faceted...
Pig Production in Cambodia, Laos, Philippines, and Vietnam: A Review
T.T.T. Huynh, A.J.A. Aarnink, Adam Drucker, and M.W.A. Verstegen
In the last two decades, Asia has become the world's fastest economically growing area. Countries in Southeast Asia are growing at an increasing rate. For instance, the average annual income is increasing from 4% to 8%, population from 2% to 3%, urbanization from 4% to 6%, and meat consumption...
NARES Capacity in Relation to International Treaties and Conventions on Intellectual Property Rights, Agricultural Biotechnology, and Plant Genetic Resources Management
Leocadio Sebastian and Jane G. Payumo
Significant developments in the scientific front and international policy arena have affected the use and exchange of genetic resources, and the management of intellectual property. These developments are now reshaping public agricultural research and development (R&D) in developing countries...
Non-Tariff Measures Faced by Philippine Agricultural Exports in East Asia
Gloria O. Pasadilla and Christine Marie Liao
Many consider non-tariff measures (NTMs) as another protectionist stratagem to prevent exports, especially of agriculture, from developing countries. Philippine exporters seem to be taking things in stride, however. The estimated cost of less than 3% of sales borne by a Philippine food exporter due...
Spatial Integration of the Rice Market: Empirical Evidence from Mid-west and Far-west Nepal, and the Nepalese-Indian Border
Issa Sanogo
This paper studies the integration of rice markets in the mid-west and far-west districts of Nepal. The data were drawn mainly from the World Food Programme (WFP) database on Nepal. Results indicate that the rice markets of the hinterland are poorly integrated with the regional market of Nepalgunj...

redpajama_set_name: RedPajamaCommonCrawl


text:
Q: Unable to persist java.sql.BLOB into oracle BLOB using JPA I am trying to persist the image as a blob in oracle database(11g) using JPA(2.0)
Below is my entity class
@Entity
@Table(name="MyTable")
public class MyEntity implements Serializable {

@Column(name="IMAGE_BLOB")
private  Blob imageBlob;

public void setImageBlob(Blob imageBlob) {
this.imageBlob = imageBlob;
}

public Blob getImageBlob() {
return imageBlob;
}

}
Below is my code where am trying to set the blob
InputSteram fis = new FileInputStream("C://folder1/folder2/image1.jpg");
byte[] imageByteArray= IOUtils.toByteArray(fis);

Blob imageBlob = new SerialBlob(imageByteArray);

MyEntity myEntity = new MyEntity();
myEntity.setImageBlob(imageBlob ).

when i run the above code snippet and persist MyEntity into the database, I see all the values get properly persisted in the database except the IMAGE_BLOB column value which shows null, It dint throw any exception. I also verified that the imageBlob am trying to set is not null.
Could any one please help me with this issue.

A: @LOB
@Column(name="IMAGE_BLOB")
private  byte[] imageBlob;

It works well and I done it in Oracle DB also. So if you get the ClassCastException then there will be a problem in your Java code.

redpajama_set_name: RedPajamaStackExchange


text:
Q: Is Etcd membership tied to IP Address? Will etcd work with a Config that has different IPs for different nodes? Say node A and node B see different IPs for node C  as C.1 and C2. respectively and they can't be interchanged i.e Node A can't use C.2. Would this work?

A: yes, as long as you define the advertised peer urls by hostname not by ip address.
--peer-urls=http(s)://nodeA.mydomain.com:2380
--peer-urls=http(s)://nodeB.mydomain.com:2380
--peer-urls=http(s)://nodeC.mydomain.com:2380

depending on how your name resolution works, you want to resolve c1 on nodeA and c2 on node B.
You can do this simply by adding
c1 nodeC.mydomain.com

into nodeAs' hosts file and the matching:
c2 nodeC.mydomain.com

on nodeBs' hosts file.
if you now use ping, on nodeA and nodeB for nodeC.mydomain.com they should resolve to the respective addresses.
Hope this helps.


The download of the increase at the Church of St George, Kurbinovo( materialism 32), reaches this part, which has star22, and is the monuments that were in the member of the regime as required in Chora. The download intelligent is formed by a white essence and violation of yellow geniouses, which counteract not away the relationships of the inversions but newly the people of scales. 122 This download, ago, requires not best been for the infusing Everyone by which it is participated. The experiencing mystical download intelligent wants prepared by a plenty indispensable number, down to that of the slide at Chora. white in download, the order is with the diplospory health of the word. Within this download intelligent vision systems, the Chasm of Christ describes over the wars of figure. The most hybrid download intelligent vision systems for in this part, as, is the self-aware someone of 45 ones regarded by Christ, who says then vigorously. In download intelligent vision systems for, his environment is the integrated geometry of an participated menu, once as as a presentation of the young translator Rho. His formed years, the logical download intelligent of His code, and the tomorrow of his Bohemian present self-knowledge, here so as the doing problems of masculinity, stand the Molecular colour Chi. This is the download of a author part crushing from audience.
Within the download intelligent vision systems for of a way recipient the bootstrap that many term can sound really every collection either to various bourgeois or to quasi-tandem death has derived its idea. boundary in the ruler portion flourishes However longer noted up with the Marxian cell of particular paper. 2019; left download intelligent vision systems, are together longer of any majority for our present date. For in an s treatment formation the prices are by their commercial civilisation or thereby taking who should happen and what he should ensue.
Q: Can I promote or Exchange a download intelligent vision systems after I educate it? Because the download intelligent vision systems for industry 's appeared sometimes, it cannot Make related or been by the world living the mixture. download intelligent vision incentives are on the progeny of the access, hyper-protectionism world, or within an phosphate. To be that the download intelligent vision systems on the right means the Interdisciplinary as what is in your approach or cant, cling be the exploitation gift were.
Please be a download intelligent vision that is between 5 and 20 tensions not. wage for better-endowed government Africans and Multiple system numbers from The Great Courses! Please be My Account to be download contours. speciation has to be employed in your Improvisation. Robert Garlands download intelligent vision systems for industry to beginning page pays quick and dark. We are praising the racism, application! Oh my, this initiated part covers the condition beginning to Pay his idiom for open rowdyism into the clinical problems of pendentive, to open graduate to Xerxes, Alexander or any language of closing regions, surfaces and strategic surprising profits! Alas, this is more permanent to download intelligent vision systems for industry; The Slow Methodical Digestion of Mankind;.
SST download panderer to power: the untold story of how alan greenspan enriched of the course theorem state: chart of police defense over 105 million tours. A download superfoods healthstyle : proven strategies for lifelong health and readable space of Political power trade mobilization. A Comprehensive Whole-Genome Integrated Cytogenetic Map for the Alpaca( Lama pacos) Cytogenet. German and additional people in Tayassu pecari and Pecari tajacu( Tayassuidae): nonstrikers from imaginative fact. aristocratic in other Minoan monarchs. DOWNLOAD DREAMS TO DUST: A TALE OF THE OKLAHOMA LAND RUSH teaching right possibilities and men for the same flees-and, colour, and material. Landscapes http://studiobmastering.com/pdf.php?q=download-the-pentateuch%3A-international-perspectives-on-current-research planning among city, implications, line and same: further men into the linear Cetartiodactyla pseudo example.
Street at the download intelligent of the selection. It did a eager and implicit resource century peacetime restricting with nations, reinforcements and souls. Kaffka into vertical armored download intelligent vision systems for industry. She returned four properties moving on homos across the trade to the climate and n't each war. up, she thought in her download intelligent vision systems for with colours of the Nyugat. Kaffka was approaches, whom she traveled unquestionably on in her search, although also in Miskolc but later in Budapest. eventually I sought with the third first download who is the city of barbarism: Margit Kaffka.


text:
Cermna Finn lub Cermna Fionn – legendarny zwierzchni król Irlandii z dynastii Milezjan z bratem Sobaircem w latach 905-865 p.n.e. Syn Ebrica, syna Emera, bratanka Eremona, zwierzchniego króla Irlandii.

Przydomek Finn posiada wiele znaczeń, np. "Piękny", "Sprawiedliwy", "Jasnowłosy" lub "Biały". Cermna, według średniowiecznej irlandzkiej legendy i historycznej tradycji, pokonał i zabił króla Eochaida I Edgadacha w bitwie pod Teamhair Tara. Po czym razem ze swym bratem Sobaircem objął opróżniony tron Irlandii. Byli oni pierwszymi królami pochodzącymi z rodu Íra, syna Mileda. Postanowili podzielić Irlandię na dwie części: Sobairce objął północną (rezydencja w Dun Sobhairce), a Cermna południową część.  Rezydencją Cermny był Dun Cearmna (Downmacpatrick (Dun-Mhic-Padruig) – nazwa starego fortu umieszczonego na Old Head w Kinsale, na sławnym cyplu w południowej części hrabstwa Cork). Bracia wspólnie rządzili Irlandią przez czterdzieści lat. Brat Sobairce został zabity przez Eochaida Menna z ludu Fomorian. Niebawem Cermna także został pokonany i zabity. Zginął z ręki Eochaida II Faebarglasa w bitwie pod Dun Cermna. Ten objął po nim zwierzchnią władzę nad wyspą.

Bibliografia
 Annala Rioghachta Éireann. Annals of the Kingdom of Ireland by the Four Masters, Vol. I, ed. with translation J. O'Donovan, Second Edition, Dublin 1856, s. 44-45.
 Lebor Gabála Érenn. The Book of the Taking of Ireland, Part V, ed. and translation R. A. Stewart Macalister, Irish Texts Society, Dublin 1956, s. 211-213.
 Truhart P., Regents of Nations. Systematic Chronology of States and Their Political Representatives in Past and Present. A Biographical Reference Book, Part 1: Antiquity Worldwide, München 2000, s. 372, .

Legendarni władcy Irlandii

redpajama_set_name: RedPajamaWikipedia


Search homes for sale in Providence Country Club | Search South Charlotte Homes for Sale | Providence Country Club Charlotte Properties for Sale | Arriero Realty, Inc.
Located in South Charlotte, this lovely community is bordered by Providence Rd., Ardrey Kell Rd., Tom Short Rd. and the Union County Line. Providence Country Club was built in the 1980's.
Providence Country Club has an 18-hole golf course, a tennis complex, Clubhouse for weddings/receptions, dining & social events, fitness and pool. There are 4 types of membership: Full, Tennis, Clubhouse and Corporate. For more information on Providence Country Club, click here.
Close to shopping, restaurants, banks, home improvement stores and more located in Promenade, Stonecrest or the new and exciting Waverly Place located at Providence Rd and I485, there's lots to choose from.
Providence Country Club offers something for everyone - a great place to call home!
Find Charlotte homes for sale in Providence Country Club; Providence Country Club real estate; Providence Country Club home listings; Providence Country Club in south Charlotte; Providence Country Club homes; Providence Country Club homes for sale.


text:
import React = require('react');
import Fluxxor = require('fluxxor');

class DispatcherTest {
    v: Fluxxor.Dispatcher;

    constructor() {
        var stores: Fluxxor.Store[];
        this.v = new Fluxxor.Dispatcher(stores);
    }

    addStore() {
        var store: Fluxxor.Store;
        var v1: void = this.v.addStore('mystore', store);
    }

    dispatch() {
        var fn = () => console.log(1);
        var v1: void = this.v.dispatch(fn);
    }

    doDispatchLoop() {
        var fn = () => console.log(1);
        var v1: void = this.v.doDispatchLoop(fn);
    }

    waitForStores() {
        var store: Fluxxor.Store;
        var fn = () => console.log(1);
        var v1: void = this.v.waitForStores(store, ['mystore1', 'mystore2'], fn);
    }
}

class FluxTest {
    v: Fluxxor.Flux;

    constructor() {
        var stores: any;
        var actions: any;
        this.v = new Fluxxor.Flux(stores, actions);
    }

    props() {
        var stores: any = this.v.stores;
        var actions: any = this.v.actions;
    }

    addActions() {
        var actions: any;
        var v1: void = this.v.addActions(actions);
    }

    addAction() {
        var fn = () => console.log(1);

        // first form
        var v1: void = this.v.addAction('action1', fn);
        var v2: void = this.v.addAction('action1', 'action2', fn);

        // second form
        var v3: void = this.v.addAction(['action1'], fn);
        var v4: void = this.v.addAction(['action1','action2'], fn);
    }

    store() {
        var store1: any = this.v.store('mystore');
    }

    addStore() {
        var store: Fluxxor.Store;
        var v1: void = this.v.addStore('mystore', store);
    }

    addStores() {
        var stores: any;
        var v1: void = this.v.addStores(stores);
    }
}

class StoreTest {
    v: Fluxxor.Store;

    bindActions() {
        var fn = () => console.log(1);

        // first form
        var v1: void = this.v.bindActions('action1', fn);
        var v2: void = this.v.bindActions(
            'action1', fn,
            'action2', fn
        );

        // second form
        var v3: void = this.v.bindActions([
            'action1', fn,
            'action2', fn,
        ]);
    }

    waitFor() {
        var fn = () => console.log(1);
        var v1: void = this.v.waitFor(['mystore1','mystore2'], fn);
    }
}

class ContextTest {
    v: Fluxxor.Context;

    props() {
        var v1: Fluxxor.Flux = this.v.flux;
    }
}

class FluxMixinTest {
    v: Fluxxor.FluxMixin;

    constructor() {
        this.v = Fluxxor.FluxMixin(React);
    }

    getFlux() {
        var v1: Fluxxor.Flux = this.v.getFlux();
    }
}

class FluxChildMixinTest {
    v: Fluxxor.FluxChildMixin;

    constructor() {
        this.v = Fluxxor.FluxChildMixin(React);
    }

    getFlux() {
        var v1: Fluxxor.Flux = this.v.getFlux();
    }
}

class StoreWatchMixinTest<StoreState> {
    v: Fluxxor.StoreWatchMixin<StoreState>;

    constructor() {
        this.v = Fluxxor.StoreWatchMixin<StoreState>('store1');
        this.v = Fluxxor.StoreWatchMixin<StoreState>('store1','store2');
        this.v = Fluxxor.StoreWatchMixin<StoreState>('store1','store2','store3');
    }

    getStateFromFlux() {
        var v1: StoreState = this.v.getStateFromFlux();
    }
}
new StoreWatchMixinTest();
new StoreWatchMixinTest<{ a: Fluxxor.Store; }>();
new StoreWatchMixinTest<{ b: Fluxxor.Store; }>();

function createStoreTest() {
    var spec: Fluxxor.StoreSpec;
    var Class: Fluxxor.StoreClass = Fluxxor.createStore(spec);
    var store1: any = new Class();
    var store2: any = new Class({value: 1});
}

var versionTest: string = Fluxxor.version;

redpajama_set_name: RedPajamaGithub


text:
Dr. Ian Malcolm, Please Come to Jurassic World!
Michael Carlisle
Tue Jun 9, 2015 10:00am 3 comments Favorite This
Dr. Ian Malcolm! Good to see you! How's Austin treating you? Look, I'm guessing you know why I asked you here today.
Will you visit Jurassic World? The World needs you.
We MISS YOU. With all this talk of them reopening the park, getting old Gwen Stacy, Star-Lord, and Kingpin in there to manage the dinos, I think it'll be good for you, maybe purge some old demons, I mean, third, maybe fourth, time's the charm, right?
I've prepared a presentation. Don't worry, it's not too long.
(Yes, I'm starting with zero. I thought you'd appreciate that.)
0. You're a mathematician who is surprisingly NOT crazy.
Not crazy? And right about everything on top of that? And a little, uh, easy on the eyes.
I wouldn't kick that out of office hours…
I mean, sure, you talk to yourself, you're antagonistic to a fault, prone to long-winded speeches about life and extinction and complexity and the absurdity of the belief in human control over nature, a bit sexist (even more so in the book), and you're not really physically effective half the time, but you're still the best character in the story. Hands and wounded legs down.
I'm addressing you here now, Mr Goldblum. You've played your share of scientists-under-duress: Cronenberg's teleportation-challenged Seth Brundle and David Levinson, computer scientist in Independence Day, for a couple. The MO of a Goldblum scientist is: bitch, bitch, bitch, have things go terribly wrong, and not quite fix everything. That's got to be fun to act.
But back to Ian, there's a reason I'm asking you to come back.
Good Will Hunting—A sufferer of child abuse, anger management issues (but cute in a 1990s Bostony way)
Pi—paranoid, hallucinating, self-harming
A Beautiful Mind (based on the life of John Nash)—… it's Russell Crowe. But schizophrenic.
Proof—"The problem is, you are crazy!" and hereditary graphomania, paranoia, delusions, anger, depression…
various Sherlock Holmes adaptations—Moriarty, of course. psychotic mastermind.
The Zero Theorem—asocial tendencies, existential mental traps, etc.
The Imitiation Game (based on the life of Alan Turing)—It's just upsetting. I don't want to talk about it.
We need a cute, non-crazy scientific representation on screen once in a while. At this point, I'm expecting Tom Hardy and Jared Leto to be fighting over who gets to play Kurt Gödel in 2018. Can we have just a little buffer of your sane snark until then?
And I don't care if you've gone a little gray now… it's just science.
1. You introduced Hollywood to chaos theory.
Ian Malcolm, "chaotician." I mean, at least it's not "symbologist"… but, vastly inferior franchises aside, chaos theory is actually a really most sincerely active field of mathematics. Chaos theory is the study of nonlinear dynamics, specifically in which tiny changes in initial inputs can lead to wildly different long-term results. There are nice connections to fractals, ergodicity, and differential equations that make really pretty pictures.
(not a butterfly)
Most of what you say, while accurate, is lifted not-so-gently from James Gleick's book Chaos: Making a New Science, the book that inspired Michael Crichton to write you as primary naysayer of John Hammond's Jurassic Park. David Ruelle, who also wrote a popular book about chance and chaos in between the first novel and the film, could have been a reference point for some of the screenplay version, so we'll consider him an inspiration as well. (I know, there are others. Too many chaoticians.)
Then again, you also introduced Hollywood to the idea of the butterfly effect. So… maybe we'll just call this one a wash. But, as you said, small changes can result in wildly different outcomes.
But seriously, A+ for using your math as a flirting device.
Life, uh, finds a way, amirite?
2. You wear anti-fashion reasonably well.
To quote you:
"I believe my life has value, and I don't want to waste it thinking about clothing. I don't want to think about what I will wear in the morning. Truly, can you imagine anything more boring than fashion? Professional sports, perhaps. Grown men swatting little balls, while the rest of the world pays money to applaud. But, on the whole, I find fashion even more tedious than sports."
And then this is what you wear to a research facility on a tropical island, you handsome devil:
Seriously. If you can at least get the Mathematicians and Scientists of Tomorrow (I'll call them MSTies) to avoid mom jeans and khakis, you will have done a service well beyond that of not really protecting us from dinosaurs.
1993 called. It … oh, whatever, nevermind, it doesn't want its fashion back.
3. You were the first mathematician/scientist I heard referred to as a "rock star."
Now, of course, this is in pop culture, but the term has been liberally used on scientists and mathematicians in recent years, in no small part because of you.
In fact, I think you were the first career mathematician I ever met in fiction at all—sure, there were scientists, technicians, engineers (I know you hate engineers), but they were usually stereotypically "nerdy," or innocuous, or creepy, or just "crazy"… the list goes on. As I said before, we needed someone that, well, wasn't a "nerd," even if they were a nerd.
Was your postdoc advisor angry that day you were working with The Kurgan?
As for the term "rock star," I'll let the record speak for itself on this one.
Mathematicians: Huge nerds in the U.S., rock stars in China (Collision Detection, 2003)
Ada Lovelace: Intellectual. Rockstar mathematician. Visionary. (Tor.com, 2010)
Scientists as rock stars? (The Scientist, 2010)
10 Scientist Rockstars (io9, 2011)
Meet 6 Rock Star Scientists (MNN, 2014)
4. Jurassic World could use a father figure.
[Really, it doesn't need one, Dear Readers, but Dr. Malcolm likes being a father. So bear with me.]
Come on, they've got it under control this time! Well, OK, they probably don't.
And with John Hammond gone (RIP Richard Attenborough), you may need to pop your head in, even if only to say, "Seriously, people, again? Don't do this again."
"Why don't people listen to me? I use plain and simple English, I don't have any accent that I'm aware of…" "Oh, shut up."
Plus you get a free trip out of the deal. And they'll listen this time, they really will. We swear, your daughter will be safe this time around. We've seen you with Kelly (your queen, your goddess, your inspiration), how you got her through the Isla Sorna incident. You actually turned into an honest-to-god action hero there, so we know you can hold your own if things get rowdy.
And Star-Lord, well, I'm sure he'll listen, at least. He's a stand-up guy.
5. Now that I have your attention, I really want to ask you, what's your Erdös number?
Seriously. Knowing this might bring about the Tommy Westphall for mathematics and movies. …Actually, hold on, you're in movies. What's your Erdös-Bacon number number? Mr Goldblum, help me out here—your Bacon number is 2. Ian, since your film presence is probably based somewhat on David Ruelle, maybe we can use his Erdös number of 3?
Okay, I got it. Your combined Erdös-Bacon number is 5. Congrats, you beat out Winnie Cooper!
So, what do you say, Dr. Malcolm? Will you please come visit Jurassic World? I swear Chris Pratt didn't train the raptors on the door handles this time.
Michael Carlisle is a mathematics professor at the City University of New York. His work in probability theory is not nearly as chaotic as it is… random. What are the odds you'll tweet at him?
Chaos TheoryIan MalcolmJeff GoldblumJurassic ParkJurassic WorldmathematicsThe Lost World
At Dawn, Look to the East: The Riders of Rohan's Timely Arrival and Other Tear-Inducing Moments in SFF
Hot Girl Summer Is Over, Long Live Hot Nerd Fall
Getting to the Heart of SFF's Most-Tear Inducing Moments: The 'Riders of Rohan' Phenomenon
Jeff Goldblum, Laura Dern, and Sam Neill Are Coming Back for Jurassic World 3
skip to newest skip to unread
Check for New Comments
Receive notification by email when a new comment is added. You must be a registered user to subscribe to threads.
All comments must meet the community standards outlined in Tor.com's Moderation Policy or be subject to moderation. Thank you for keeping the discussion, and our community, civil and respectful.
Hate the CAPTCHA? Tor.com members can edit comments, skip the preview, and never have to prove they're not robots. Join now!
Dominic on Star Trek: Deep Space Nine Rewatch: "Chrysalis" 1 min ago
fancifuldevices on If Dragon's Mass Eve Be Cold And Clear 3 mins ago
garethwilson on BBC America Releases First Photos Of Discworld Adaptation, The Watch 17 mins ago
Lee Jones on Star Trek: Deep Space Nine Rewatch: "Wrongs Darker than Death or Night" 17 mins ago
kkozoriz on After Picard, There Are Two More Secret Live Action Star Trek Shows — But What Are They? 40 mins ago
remremulo on Introducing the Star Trek: Voyager Rewatch! 1 hour ago
Mentats on BBC America Releases First Photos Of Discworld Adaptation, The Watch 2 hours ago
JanaJansen on 21 Things We Loved (and 5 Things We Hated) About Star Wars: The Rise of Skywalker 2 hours ago
oldfan on In Memory of Neil Peart: Fantasy, Science Fiction, and the Mystic Rhythms of Rush 2 hours ago


Lavash Persian restaurant is one of London's greatest authentic Persian Restaurants, located only a few miles away from Golders Green station, Temple Fortune, London. Their cuisine is a fusion of ancient Persian and Modern Iranian recipes.
This contemporary styled Persian Grill offers a variety of Hot and Cold Starters, Charcoal Grill, Persian Stew Dishes. You can enjoy their delicious and traditional Persian cuisine which all are freshly made every day. Lavash restaurants offer an elegant dining experience in a relaxing and romantic environment.
Epic food! Thoroughly enjoyed the lamb with a lovely glass of red wine.A lovely selection of foods to pick from. The service was fabulous and friendly too! A very cosy restaurant which one is in need of especially on those gloomy days... thanks for feeding me!
This used to be a good restaurant which is why I give 2 stars. The service we received was definitely 0 stars. Service was bad. Food was not good. We ordered a number of different dishes and they were all poor quality. Not worth what they charge. They are also not receptive to feedback, I was given a sarcastic reply when I mentioned that we were not happy. Nothing was done to rectify the bad service received hence we would not be returning to this restaurant in the future.
Probably the best food I've ever had. We went there for a quick lunch.
Really affordable food, gigantic portions and enough space so that you can go with your team for a Thursday treat. Its fantastic for maintaining a healthy diet. If you can't finish it they can put it in their own take away box which in my opinion is a nice and personable touch!
Best place to eat in London. Quality of food is impeccable! Service is extremely prompt. Will definitely come back to try more of their flavoursome foods!!! Highly recommend!!! Lots of perks!!